<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Appendix B Errors, Error Codes, and Common Problems</title>
<link rel="stylesheet" href="mvl.css" type="text/css" />
<meta name="generator" content="DocBook XSL Stylesheets + chunker.py v1.9.2" />
<link rel="start" href="index.html" title="{book-title}" />
<link rel="up" href="" title="" />
<link rel="prev" href="faqs.html" title="Appendix A MySQL 5.7 Frequently Asked Questions" />
<link rel="next" href="indexes.html" title="Appendix C Indexes" />
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr>
<th colspan="3" align="center">Appendix B Errors, Error Codes, and Common Problems</th>
</tr>
<tr>
<td width="20%" align="left"><a accesskey="p" href="faqs.html">Prev</a> </td>
<th width="60%" align="center"></th>
<td width="20%" align="right"> <a accesskey="n" href="indexes.html">Next</a></td>
</tr>
</table>
<hr>
</div>
<div class="appendix">
<div class="titlepage">
<div>
<div>
<h1 class="title"><a name="error-handling"></a>Appendix B Errors, Error Codes, and Common Problems</h1>

</div>

</div>

</div>
<div class="toc">
<p><b>Table of Contents</b></p><dl class="toc"><dt><span class="section"><a href="error-handling.html#error-message-components">B.1 Error Message Sources and Components</a></span></dt><dt><span class="section"><a href="error-handling.html#error-interfaces">B.2 Error Information Interfaces</a></span></dt><dt><span class="section"><a href="error-handling.html#error-reference">B.3 Error Message Reference</a></span></dt><dd><dl><dt><span class="section"><a href="error-handling.html#server-error-reference">B.3.1 Server Error Message Reference</a></span></dt><dt><span class="section"><a href="error-handling.html#client-error-reference">B.3.2 Client Error Message Reference</a></span></dt><dt><span class="section"><a href="error-handling.html#global-error-reference">B.3.3 Global Error Message Reference</a></span></dt></dl></dd><dt><span class="section"><a href="error-handling.html#problems">B.4 Problems and Common Errors</a></span></dt><dd><dl><dt><span class="section"><a href="error-handling.html#what-is-crashing">B.4.1 How to Determine What Is Causing a Problem</a></span></dt><dt><span class="section"><a href="error-handling.html#common-errors">B.4.2 Common Errors When Using MySQL Programs</a></span></dt><dt><span class="section"><a href="error-handling.html#administration-issues">B.4.3 Administration-Related Issues</a></span></dt><dt><span class="section"><a href="error-handling.html#query-issues">B.4.4 Query-Related Issues</a></span></dt><dt><span class="section"><a href="error-handling.html#optimizer-issues">B.4.5 Optimizer-Related Issues</a></span></dt><dt><span class="section"><a href="error-handling.html#table-definition-issues">B.4.6 Table Definition-Related Issues</a></span></dt><dt><span class="section"><a href="error-handling.html#known-issues">B.4.7 Known Issues in MySQL</a></span></dt></dl></dd></dl>
</div>
<p>
    This appendix describes the types of error information MySQL
    provides and how to obtain information about them. It also lists the
    error messages that the MySQL server and MySQL client programs
    generate. The final section is for troubleshooting. It describes
    common problems and errors that may occur and potential resolutions.
</p>
<h2><a name="idm46734193462544"></a>Additional Resources</h2>
<p>
    Other sections that discuss error-related topics include:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
        Information about configuring where and how the server writes
        the error log: <a class="xref" href="server-administration.html#error-log" title="5.4.2 The Error Log">Section 5.4.2, “The Error Log”</a>
      </p></li><li class="listitem"><p>
        Information about the character set used for error messages:
        <a class="xref" href="charset.html#charset-errors" title="10.6 Error Message Character Set">Section 10.6, “Error Message Character Set”</a>
      </p></li><li class="listitem"><p>
        Information about the language used for error messages:
        <a class="xref" href="charset.html#error-message-language" title="10.12 Setting the Error Message Language">Section 10.12, “Setting the Error Message Language”</a>
      </p></li><li class="listitem"><p>
        Information about errors related to
        <a class="link" href="innodb-storage-engine.html" title="Chapter 14 The InnoDB Storage Engine"><code class="literal">InnoDB</code></a>:
        <a class="xref" href="innodb-storage-engine.html#innodb-error-handling" title="14.22.4 InnoDB Error Handling">Section 14.22.4, “InnoDB Error Handling”</a>
</p></li></ul>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name="error-message-components"></a>B.1 Error Message Sources and Components</h2>

</div>

</div>

</div>
<p>
      This section discusses how error messages originate within MySQL
      and the components they contain.
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><a class="xref" href="error-handling.html#error-sources" title="Error Message Sources">Error Message Sources</a></p></li><li class="listitem"><p><a class="xref" href="error-handling.html#error-components" title="Error Message Components">Error Message Components</a></p></li></ul>
</div>

<div class="simplesect">

<div class="titlepage">
<div>

<div class="simple">
<h3 class="title"><a name="error-sources"></a>Error Message Sources</h3>

</div>

</div>

</div>
<p>
        Error messages can originate on the server side or the client
        side:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
            On the server side, error messages may occur during the
            startup and shutdown processes, as a result of issues that
            occur during SQL statement execution, and so forth.
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p>
                The MySQL server writes some error messages to its error
                log. These indicate issues of interest to database
                administrators or that require DBA action.
              </p></li><li class="listitem"><p>
                The server sends other error messages to client
                programs. These indicate issues pertaining only to a
                particular client. The MySQL client library takes errors
                received from the server and makes them available to the
                host client program.
</p></li></ul>
</div>
</li><li class="listitem"><p>
            Client-side error messages are generated from within the
            MySQL client library, usually involving problems
            communicating with the server.
</p></li></ul>
</div>
<p>
        Example server-side error messages written to the error log:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
            This message produced during the startup process provides a
            status or progress indicator:
          </p><pre data-lang="none" class="programlisting">2018-09-26T14:46:06.326016Z 0 [Note] Skipping generation of SSL
certificates as options related to SSL are specified.</pre></li><li class="listitem"><p>
            This message indicates an issue that requires DBA action:
          </p><pre data-lang="none" class="programlisting">2018-10-02T03:20:39.410387Z 0 [ERROR] Plugin 'InnoDB'
registration as a STORAGE ENGINE failed.</pre></li></ul>
</div>
<p>
        Example server-side error message sent to client programs, as
        displayed by the <a class="link" href="programs.html#mysql" title="4.5.1 mysql — The MySQL Command-Line Client"><span class="command"><strong>mysql</strong></span></a> client:
      </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>SELECT * FROM no_such_table;</code></strong>
ERROR 1146 (42S02): Table 'test.no_such_table' doesn't exist
</pre><p>
        Example client-side error message originating from within the
        client library, as displayed by the <a class="link" href="programs.html#mysql" title="4.5.1 mysql — The MySQL Command-Line Client"><span class="command"><strong>mysql</strong></span></a>
        client:
      </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>mysql -h no-such-host</code></strong>
ERROR 2005 (HY000): Unknown MySQL server host 'no-such-host' (0)
</pre><p>
        Whether an error originates from within the client library or is
        received from the server, a MySQL client program may respond in
        varying ways. As just illustrated, the client may display the
        error message so the user can take corrective measures. The
        client may instead internally attempt to resolve or retry a
        failed operation, or take other action.
</p>
</div>
<div class="simplesect">
<div class="titlepage">
<div>
<div class="simple">
<h3 class="title"><a name="error-components"></a>Error Message Components</h3>

</div>

</div>

</div>
<p>
        When an error occurs, error information includes several
        components: an error code, SQLSTATE value, and message string.
        These components have the following characteristics:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
            Error code: This value is numeric. It is MySQL-specific and
            is not portable to other database systems.
          </p><p>
            Each error number has a corresponding symbolic value.
            Examples:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p>
                The symbol for server error number
                <code class="literal">1146</code> is
                <a class="link" href="error-handling.html#error_er_no_such_table"><code class="literal">ER_NO_SUCH_TABLE</code></a>.
              </p></li><li class="listitem"><p>
                The symbol for client error number
                <code class="literal">2005</code> is
                <a class="link" href="error-handling.html#error_cr_unknown_host"><code class="literal">CR_UNKNOWN_HOST</code></a>.
</p></li></ul>
</div>
<p>
            Error codes are stable across General Availability (GA)
            releases of a given MySQL series. Before a series reaches GA
            status, new codes may still be under development and are
            subject to change.
          </p></li><li class="listitem"><p>
            SQLSTATE value: This value is a five-character string (for
            example, <code class="literal">'42S02'</code>). SQLSTATE values are
            taken from ANSI SQL and ODBC and are more standardized than
            the numeric error codes. The first two characters of an
            SQLSTATE value indicate the error class:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p>
                Class = <code class="literal">'00'</code> indicates success.
              </p></li><li class="listitem"><p>
                Class = <code class="literal">'01'</code> indicates a warning.
              </p></li><li class="listitem"><p>
                Class = <code class="literal">'02'</code> indicates <span class="quote">“<span class="quote">not
                found.</span>”</span> This is relevant within the context of
                cursors and is used to control what happens when a
                cursor reaches the end of a data set. This condition
                also occurs for <code class="literal">SELECT ... INTO
                <em class="replaceable"><code>var_list</code></em></code> statements
                that retrieve no rows.
              </p></li><li class="listitem"><p>
                Class &gt; <code class="literal">'02'</code> indicates an
                exception.
</p></li></ul>
</div>
<p>
            For server-side errors, not all MySQL error numbers have
            corresponding SQLSTATE values. In these cases,
            <code class="literal">'HY000'</code> (general error) is used.
          </p><p>
            For client-side errors, the SQLSTATE value is always
            <code class="literal">'HY000'</code> (general error), so it is not
            meaningful for distinguishing one client error from another.
          </p></li><li class="listitem"><p>
            Message string: This string provides a textual description
            of the error.
</p></li></ul>
</div>

</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name="error-interfaces"></a>B.2 Error Information Interfaces</h2>

</div>

</div>

</div>
<a class="indexterm" name="idm46734193405664"></a><a class="indexterm" name="idm46734193404208"></a><p>
      Error messages can originate on the server side or the client
      side, and each error message includes an error code, SQLSTATE
      value, and message string, as described in
      <a class="xref" href="error-handling.html#error-message-components" title="B.1 Error Message Sources and Components">Section B.1, “Error Message Sources and Components”</a>. For lists of
      server-side, client-side, and global (shared between server and
      clients) errors, see <a class="xref" href="error-handling.html#error-reference" title="B.3 Error Message Reference">Section B.3, “Error Message Reference”</a>.
    </p><p>
      For error checking from within programs, use error code numbers or
      symbols, not error message strings. Message strings do not change
      often, but it is possible. Also, if the database administrator
      changes the language setting, that affects the language of message
      strings; see <a class="xref" href="charset.html#error-message-language" title="10.12 Setting the Error Message Language">Section 10.12, “Setting the Error Message Language”</a>.
    </p><p>
      Error information in MySQL is available in the server error log,
      at the SQL level, from within client programs, and at the command
      line.
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><a class="xref" href="error-handling.html#error-interface-log" title="Error Log">Error Log</a></p></li><li class="listitem"><p><a class="xref" href="error-handling.html#error-interface-sql" title="SQL Error Message Interface">SQL Error Message Interface</a></p></li><li class="listitem"><p><a class="xref" href="error-handling.html#error-interface-client" title="Client Error Message Interface">Client Error Message Interface</a></p></li><li class="listitem"><p><a class="xref" href="error-handling.html#error-interface-command" title="Command-Line Error Message Interface">Command-Line Error Message Interface</a></p></li></ul>
</div>

<div class="simplesect">

<div class="titlepage">
<div>

<div class="simple">
<h3 class="title"><a name="error-interface-log"></a>Error Log</h3>

</div>

</div>

</div>
<p>
        On the server side, some messages are intended for the error
        log. For information about configuring where and how the server
        writes the log, see <a class="xref" href="server-administration.html#error-log" title="5.4.2 The Error Log">Section 5.4.2, “The Error Log”</a>.
      </p><p>
        Other server error messages are intended to be sent to client
        programs and are available as described in
        <a class="xref" href="error-handling.html#error-interface-client" title="Client Error Message Interface">Client Error Message Interface</a>.
</p>
</div>
<div class="simplesect">
<div class="titlepage">
<div>
<div class="simple">
<h3 class="title"><a name="error-interface-sql"></a>SQL Error Message Interface</h3>

</div>

</div>

</div>
<p>
        At the SQL level, there are several sources of error information
        in MySQL:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
            SQL statement warning and error information is available
            through the <a class="link" href="sql-statements.html#show-warnings" title="13.7.5.40 SHOW WARNINGS Statement"><code class="literal">SHOW WARNINGS</code></a> and
            <a class="link" href="sql-statements.html#show-errors" title="13.7.5.17 SHOW ERRORS Statement"><code class="literal">SHOW ERRORS</code></a> statements. The
            <a class="link" href="server-administration.html#sysvar_warning_count"><code class="literal">warning_count</code></a> system
            variable indicates the number of errors, warnings, and notes
            (with notes excluded if the
            <a class="link" href="server-administration.html#sysvar_sql_notes"><code class="literal">sql_notes</code></a> system variable
            is disabled). The
            <a class="link" href="server-administration.html#sysvar_error_count"><code class="literal">error_count</code></a> system variable
            indicates the number of errors. Its value excludes warnings
            and notes.
          </p></li><li class="listitem"><p>
            The <a class="link" href="sql-statements.html#get-diagnostics" title="13.6.7.3 GET DIAGNOSTICS Statement"><code class="literal">GET DIAGNOSTICS</code></a> statement
            may be used to inspect the diagnostic information in the
            diagnostics area. See <a class="xref" href="sql-statements.html#get-diagnostics" title="13.6.7.3 GET DIAGNOSTICS Statement">Section 13.6.7.3, “GET DIAGNOSTICS Statement”</a>.
          </p></li><li class="listitem"><p>
            <a class="link" href="sql-statements.html#show-slave-status" title="13.7.5.34 SHOW SLAVE STATUS Statement"><code class="literal">SHOW SLAVE STATUS</code></a> statement
            output includes information about replication errors
            occurring on replication slave servers.
          </p></li><li class="listitem"><p>
            <a class="link" href="sql-statements.html#show-engine" title="13.7.5.15 SHOW ENGINE Statement"><code class="literal">SHOW ENGINE
            INNODB STATUS</code></a> statement output includes
            information about the most recent foreign key error if a
            <a class="link" href="sql-statements.html#create-table" title="13.1.18 CREATE TABLE Statement"><code class="literal">CREATE TABLE</code></a> statement for an
            <a class="link" href="innodb-storage-engine.html" title="Chapter 14 The InnoDB Storage Engine"><code class="literal">InnoDB</code></a> table fails.
</p></li></ul>
</div>

</div>
<div class="simplesect">
<div class="titlepage">
<div>
<div class="simple">
<h3 class="title"><a name="error-interface-client"></a>Client Error Message Interface</h3>

</div>

</div>

</div>
<p>
        Client programs receive errors from two sources:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
            Errors that originate on the client side from within the
            MySQL client library.
          </p></li><li class="listitem"><p>
            Errors that originate on the server side and are sent to the
            client by the server. These are received within the client
            library, which makes them available to the host client
            program.
</p></li></ul>
</div>
<p>
        Regardless of whether an error originates from within the client
        library or is received from the server, a MySQL client program
        obtains the error code, SQLSTATE value, message string, and
        other related information by calling C API functions in the
        client library:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
            <a class="link" href="connectors-apis.html#mysql-errno" title="27.7.6.14 mysql_errno()"><code class="literal">mysql_errno()</code></a> returns the
            MySQL error code.
          </p></li><li class="listitem"><p>
            <a class="link" href="connectors-apis.html#mysql-sqlstate" title="27.7.6.72 mysql_sqlstate()"><code class="literal">mysql_sqlstate()</code></a> returns the
            SQLSTATE value.
          </p></li><li class="listitem"><p>
            <a class="link" href="connectors-apis.html#mysql-error" title="27.7.6.15 mysql_error()"><code class="literal">mysql_error()</code></a> returns the
            message string.
          </p></li><li class="listitem"><p>
            <a class="link" href="connectors-apis.html#mysql-stmt-errno" title="27.7.10.8 mysql_stmt_errno()"><code class="literal">mysql_stmt_errno()</code></a>,
            <a class="link" href="connectors-apis.html#mysql-stmt-sqlstate" title="27.7.10.27 mysql_stmt_sqlstate()"><code class="literal">mysql_stmt_sqlstate()</code></a>, and
            <a class="link" href="connectors-apis.html#mysql-stmt-error" title="27.7.10.9 mysql_stmt_error()"><code class="literal">mysql_stmt_error()</code></a> are the
            corresponding error functions for prepared statements.
          </p></li><li class="listitem"><p>
            <a class="link" href="connectors-apis.html#mysql-warning-count" title="27.7.6.78 mysql_warning_count()"><code class="literal">mysql_warning_count()</code></a>
            returns the number of errors, warnings, and notes for the
            most recent statement.
</p></li></ul>
</div>
<p>
        For descriptions of the client library error functions, see
        <a class="xref" href="connectors-apis.html#c-api" title="27.7 MySQL C API">Section 27.7, “MySQL C API”</a>.
      </p><p>
        A MySQL client program may respond to an error in varying ways.
        The client may display the error message so the user can take
        corrective measures, internally attempt to resolve or retry a
        failed operation, or take other action. For example, (using the
        <a class="link" href="programs.html#mysql" title="4.5.1 mysql — The MySQL Command-Line Client"><span class="command"><strong>mysql</strong></span></a> client), a failure to connect to the
        server might result in this message:
      </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>mysql -h no-such-host</code></strong>
ERROR 2005 (HY000): Unknown MySQL server host 'no-such-host' (0)
</pre>
</div>
<div class="simplesect">
<div class="titlepage">
<div>
<div class="simple">
<h3 class="title"><a name="error-interface-command"></a>Command-Line Error Message Interface</h3>

</div>

</div>

</div>
<p>
        The <a class="link" href="programs.html#perror" title="4.8.2 perror — Display MySQL Error Message Information"><span class="command"><strong>perror</strong></span></a> program provides information from
        the command line about error numbers. See
        <a class="xref" href="programs.html#perror" title="4.8.2 perror — Display MySQL Error Message Information">Section 4.8.2, “<span class="command"><strong>perror</strong></span> — Display MySQL Error Message Information”</a>.
      </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>perror 1231</code></strong>
MySQL error code 1231 (ER_WRONG_VALUE_FOR_VAR): Variable '%-.64s' can't
be set to the value of '%-.200s'
</pre><p>
        For MySQL NDB Cluster errors, use <a class="link" href="mysql-cluster.html#mysql-cluster-programs-ndb-perror" title="21.4.17 ndb_perror — Obtain NDB Error Message Information"><span class="command"><strong>ndb_perror</strong></span></a>.
        See <a class="xref" href="mysql-cluster.html#mysql-cluster-programs-ndb-perror" title="21.4.17 ndb_perror — Obtain NDB Error Message Information">Section 21.4.17, “<span class="command"><strong>ndb_perror</strong></span> — Obtain NDB Error Message Information”</a>.
      </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>ndb_perror 323</code></strong>
NDB error code 323: Invalid nodegroup id, nodegroup already existing:
Permanent error: Application error
</pre>
</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name="error-reference"></a>B.3 Error Message Reference</h2>

</div>

</div>

</div>
<div class="toc">
<dl class="toc"><dt><span class="section"><a href="error-handling.html#server-error-reference">B.3.1 Server Error Message Reference</a></span></dt><dt><span class="section"><a href="error-handling.html#client-error-reference">B.3.2 Client Error Message Reference</a></span></dt><dt><span class="section"><a href="error-handling.html#global-error-reference">B.3.3 Global Error Message Reference</a></span></dt></dl>
</div>
<p>
      This section provides a reference for the various types of error
      messages in MySQL:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
          Error messages produced only by the server:
          <a class="xref" href="error-handling.html#server-error-reference" title="B.3.1 Server Error Message Reference">Section B.3.1, “Server Error Message Reference”</a>
        </p></li><li class="listitem"><p>
          Error messages that originate only from within the MySQL
          client library: <a class="xref" href="error-handling.html#client-error-reference" title="B.3.2 Client Error Message Reference">Section B.3.2, “Client Error Message Reference”</a>
        </p></li><li class="listitem"><p>
          Error messages that are shared between the server and the
          client library: <a class="xref" href="error-handling.html#global-error-reference" title="B.3.3 Global Error Message Reference">Section B.3.3, “Global Error Message Reference”</a>
</p></li></ul>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="server-error-reference"></a>B.3.1 Server Error Message Reference</h3>

</div>

</div>

</div>
<p>
        The MySQL server writes some error messages to its error log,
        and sends others to client programs.
      </p><p>
        Example server-side error messages written to the error log:
      </p><pre data-lang="none" class="programlisting">2018-09-26T14:46:06.326016Z 0 [Note] Skipping generation of SSL
certificates as options related to SSL are specified.

2018-10-02T03:20:39.410387Z 0 [ERROR] Plugin 'InnoDB'
registration as a STORAGE ENGINE failed.</pre><p>
        Example server-side error message sent to client programs, as
        displayed by the <a class="link" href="programs.html#mysql" title="4.5.1 mysql — The MySQL Command-Line Client"><span class="command"><strong>mysql</strong></span></a> client:
      </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>SELECT * FROM no_such_table;</code></strong>
ERROR 1146 (42S02): Table 'test.no_such_table' doesn't exist
</pre><p>
        Each server error message includes an error code, SQLSTATE
        value, and message string, as described in
        <a class="xref" href="error-handling.html#error-message-components" title="B.1 Error Message Sources and Components">Section B.1, “Error Message Sources and Components”</a>. These components are
        available as described in <a class="xref" href="error-handling.html#error-interfaces" title="B.2 Error Information Interfaces">Section B.2, “Error Information Interfaces”</a>.
      </p><p>
        In addition to the errors in the following list, the server can
        also produce error messages that have error codes in the range
        from 1 to 999. See <a class="xref" href="error-handling.html#global-error-reference" title="B.3.3 Global Error Message Reference">Section B.3.3, “Global Error Message Reference”</a>
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><a name="error_er_hashchk"></a>
      <a class="indexterm" name="idm46734193320608"></a>

      <a class="indexterm" name="idm46734193319568"></a>

      Error number: <code class="literal">1000</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_hashchk"><code class="literal">ER_HASHCHK</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: hashchk
    </p><p>
      Unused.
    </p></li><li class="listitem"><p><a name="error_er_nisamchk"></a>
      <a class="indexterm" name="idm46734193313152"></a>

      <a class="indexterm" name="idm46734193312112"></a>

      Error number: <code class="literal">1001</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_nisamchk"><code class="literal">ER_NISAMCHK</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: isamchk
    </p><p>
      Unused.
    </p></li><li class="listitem"><p><a name="error_er_no"></a>
      <a class="indexterm" name="idm46734193305696"></a>

      <a class="indexterm" name="idm46734193304656"></a>

      Error number: <code class="literal">1002</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no"><code class="literal">ER_NO</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: NO
    </p><p>
      Used in the construction of other messages.
    </p></li><li class="listitem"><p><a name="error_er_yes"></a>
      <a class="indexterm" name="idm46734193298288"></a>

      <a class="indexterm" name="idm46734193297248"></a>

      Error number: <code class="literal">1003</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_yes"><code class="literal">ER_YES</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: YES
    </p><p>
      Used in the construction of other messages.
    </p><p>
      Extended <a class="link" href="sql-statements.html#explain" title="13.8.2 EXPLAIN Statement"><code class="literal">EXPLAIN</code></a> format generates
      Note messages. <a class="link" href="error-handling.html#error_er_yes"><code class="literal">ER_YES</code></a> is used in
      the <code class="literal">Code</code> column for these messages in
      subsequent <a class="link" href="sql-statements.html#show-warnings" title="13.7.5.40 SHOW WARNINGS Statement"><code class="literal">SHOW WARNINGS</code></a> output.
    </p></li><li class="listitem"><p><a name="error_er_cant_create_file"></a>
      <a class="indexterm" name="idm46734193285872"></a>

      <a class="indexterm" name="idm46734193284832"></a>

      Error number: <code class="literal">1004</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_create_file"><code class="literal">ER_CANT_CREATE_FILE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't create file '%s' (errno: %d - %s)
    </p><p>
      Occurs for failure to create or copy a file needed for some
      operation.
    </p><p>
      Possible causes: Permissions problem for source file; destination
      file already exists but is not writeable.
    </p></li><li class="listitem"><p><a name="error_er_cant_create_table"></a>
      <a class="indexterm" name="idm46734193277760"></a>

      <a class="indexterm" name="idm46734193276720"></a>

      Error number: <code class="literal">1005</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_create_table"><code class="literal">ER_CANT_CREATE_TABLE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't create table '%s' (errno: %d)
    </p><p>
      <code class="literal">InnoDB</code> reports this error when a table cannot
      be created. If the error message refers to error 150, table
      creation failed because a
      <a class="link" href="glossary.html#glos_foreign_key_constraint" title="FOREIGN KEY constraint">foreign key
      constraint</a> was not correctly formed. If the error message
      refers to error −1, table creation probably failed because
      the table includes a column name that matched the name of an
      internal <code class="literal">InnoDB</code> table.
    </p></li><li class="listitem"><p><a name="error_er_cant_create_db"></a>
      <a class="indexterm" name="idm46734193267504"></a>

      <a class="indexterm" name="idm46734193266448"></a>

      Error number: <code class="literal">1006</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_create_db"><code class="literal">ER_CANT_CREATE_DB</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't create database '%s' (errno: %d)
    </p></li><li class="listitem"><p><a name="error_er_db_create_exists"></a>
      <a class="indexterm" name="idm46734193260432"></a>

      <a class="indexterm" name="idm46734193259392"></a>

      Error number: <code class="literal">1007</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_db_create_exists"><code class="literal">ER_DB_CREATE_EXISTS</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't create database '%s'; database exists
    </p><p>
      An attempt to create a database failed because the database
      already exists.
    </p><p>
      Drop the database first if you really want to replace an existing
      database, or add an <code class="literal">IF NOT EXISTS</code> clause to the
      <a class="link" href="sql-statements.html#create-database" title="13.1.11 CREATE DATABASE Statement"><code class="literal">CREATE DATABASE</code></a> statement if to
      retain an existing database without having the statement produce
      an error.
    </p></li><li class="listitem"><p><a name="error_er_db_drop_exists"></a>
      <a class="indexterm" name="idm46734193250352"></a>

      <a class="indexterm" name="idm46734193249296"></a>

      Error number: <code class="literal">1008</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_db_drop_exists"><code class="literal">ER_DB_DROP_EXISTS</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't drop database '%s'; database doesn't exist
    </p></li><li class="listitem"><p><a name="error_er_db_drop_delete"></a>
      <a class="indexterm" name="idm46734193243264"></a>

      <a class="indexterm" name="idm46734193242208"></a>

      Error number: <code class="literal">1009</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_db_drop_delete"><code class="literal">ER_DB_DROP_DELETE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Error dropping database (can't delete '%s', errno: %d)
    </p></li><li class="listitem"><p><a name="error_er_db_drop_rmdir"></a>
      <a class="indexterm" name="idm46734193236224"></a>

      <a class="indexterm" name="idm46734193235168"></a>

      Error number: <code class="literal">1010</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_db_drop_rmdir"><code class="literal">ER_DB_DROP_RMDIR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Error dropping database (can't rmdir '%s', errno: %d)
    </p></li><li class="listitem"><p><a name="error_er_cant_delete_file"></a>
      <a class="indexterm" name="idm46734193229136"></a>

      <a class="indexterm" name="idm46734193228096"></a>

      Error number: <code class="literal">1011</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_delete_file"><code class="literal">ER_CANT_DELETE_FILE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Error on delete of '%s' (errno: %d - %s)
    </p></li><li class="listitem"><p><a name="error_er_cant_find_system_rec"></a>
      <a class="indexterm" name="idm46734193222048"></a>

      <a class="indexterm" name="idm46734193221008"></a>

      Error number: <code class="literal">1012</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_find_system_rec"><code class="literal">ER_CANT_FIND_SYSTEM_REC</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't read record in system table
    </p><p>
      Returned by <code class="literal">InnoDB</code> for attempts to access
      <code class="literal">InnoDB</code> <code class="literal">INFORMATION_SCHEMA</code>
      tables when <code class="literal">InnoDB</code> is unavailable.
    </p></li><li class="listitem"><p><a name="error_er_cant_get_stat"></a>
      <a class="indexterm" name="idm46734193211744"></a>

      <a class="indexterm" name="idm46734193210688"></a>

      Error number: <code class="literal">1013</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_get_stat"><code class="literal">ER_CANT_GET_STAT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't get status of '%s' (errno: %d - %s)
    </p></li><li class="listitem"><p><a name="error_er_cant_get_wd"></a>
      <a class="indexterm" name="idm46734193204720"></a>

      <a class="indexterm" name="idm46734193203664"></a>

      Error number: <code class="literal">1014</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_get_wd"><code class="literal">ER_CANT_GET_WD</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't get working directory (errno: %d - %s)
    </p></li><li class="listitem"><p><a name="error_er_cant_lock"></a>
      <a class="indexterm" name="idm46734193197696"></a>

      <a class="indexterm" name="idm46734193196656"></a>

      Error number: <code class="literal">1015</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_lock"><code class="literal">ER_CANT_LOCK</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't lock file (errno: %d - %s)
    </p></li><li class="listitem"><p><a name="error_er_cant_open_file"></a>
      <a class="indexterm" name="idm46734193190752"></a>

      <a class="indexterm" name="idm46734193189696"></a>

      Error number: <code class="literal">1016</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_open_file"><code class="literal">ER_CANT_OPEN_FILE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't open file: '%s' (errno: %d - %s)
    </p><p>
      <code class="literal">InnoDB</code> reports this error when the table from
      the <code class="literal">InnoDB</code> <a class="link" href="glossary.html#glos_data_files" title="data files">data
      files</a> cannot be found, even though the
      <code class="filename">.frm</code> file for the table exists. See
      <a class="xref" href="innodb-storage-engine.html#innodb-troubleshooting-datadict" title="14.22.3 Troubleshooting InnoDB Data Dictionary Operations">Section 14.22.3, “Troubleshooting InnoDB Data Dictionary Operations”</a>.
    </p></li><li class="listitem"><p><a name="error_er_file_not_found"></a>
      <a class="indexterm" name="idm46734193179600"></a>

      <a class="indexterm" name="idm46734193178544"></a>

      Error number: <code class="literal">1017</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_file_not_found"><code class="literal">ER_FILE_NOT_FOUND</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't find file: '%s' (errno: %d - %s)
    </p></li><li class="listitem"><p><a name="error_er_cant_read_dir"></a>
      <a class="indexterm" name="idm46734193172640"></a>

      <a class="indexterm" name="idm46734193171584"></a>

      Error number: <code class="literal">1018</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_read_dir"><code class="literal">ER_CANT_READ_DIR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't read dir of '%s' (errno: %d - %s)
    </p></li><li class="listitem"><p><a name="error_er_cant_set_wd"></a>
      <a class="indexterm" name="idm46734193165616"></a>

      <a class="indexterm" name="idm46734193164560"></a>

      Error number: <code class="literal">1019</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_set_wd"><code class="literal">ER_CANT_SET_WD</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't change dir to '%s' (errno: %d - %s)
    </p></li><li class="listitem"><p><a name="error_er_checkread"></a>
      <a class="indexterm" name="idm46734193158592"></a>

      <a class="indexterm" name="idm46734193157552"></a>

      Error number: <code class="literal">1020</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_checkread"><code class="literal">ER_CHECKREAD</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Record has changed since last read in table '%s'
    </p></li><li class="listitem"><p><a name="error_er_disk_full"></a>
      <a class="indexterm" name="idm46734193151584"></a>

      <a class="indexterm" name="idm46734193150544"></a>

      Error number: <code class="literal">1021</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_disk_full"><code class="literal">ER_DISK_FULL</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Disk full (%s); waiting for someone to free some space...
      (errno: %d - %s)
    </p></li><li class="listitem"><p><a name="error_er_dup_key"></a>
      <a class="indexterm" name="idm46734193144592"></a>

      <a class="indexterm" name="idm46734193143552"></a>

      Error number: <code class="literal">1022</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_dup_key"><code class="literal">ER_DUP_KEY</code></a>; SQLSTATE:
      <code class="literal">23000</code>
    </p><p>
      Message: Can't write; duplicate key in table '%s'
    </p></li><li class="listitem"><p><a name="error_er_error_on_close"></a>
      <a class="indexterm" name="idm46734193137712"></a>

      <a class="indexterm" name="idm46734193136656"></a>

      Error number: <code class="literal">1023</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_error_on_close"><code class="literal">ER_ERROR_ON_CLOSE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Error on close of '%s' (errno: %d - %s)
    </p></li><li class="listitem"><p><a name="error_er_error_on_read"></a>
      <a class="indexterm" name="idm46734193130672"></a>

      <a class="indexterm" name="idm46734193129616"></a>

      Error number: <code class="literal">1024</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_error_on_read"><code class="literal">ER_ERROR_ON_READ</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Error reading file '%s' (errno: %d - %s)
    </p></li><li class="listitem"><p><a name="error_er_error_on_rename"></a>
      <a class="indexterm" name="idm46734193123600"></a>

      <a class="indexterm" name="idm46734193122560"></a>

      Error number: <code class="literal">1025</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_error_on_rename"><code class="literal">ER_ERROR_ON_RENAME</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Error on rename of '%s' to '%s' (errno: %d - %s)
    </p></li><li class="listitem"><p><a name="error_er_error_on_write"></a>
      <a class="indexterm" name="idm46734193116496"></a>

      <a class="indexterm" name="idm46734193115440"></a>

      Error number: <code class="literal">1026</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_error_on_write"><code class="literal">ER_ERROR_ON_WRITE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Error writing file '%s' (errno: %d - %s)
    </p></li><li class="listitem"><p><a name="error_er_file_used"></a>
      <a class="indexterm" name="idm46734193109472"></a>

      <a class="indexterm" name="idm46734193108432"></a>

      Error number: <code class="literal">1027</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_file_used"><code class="literal">ER_FILE_USED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: '%s' is locked against change
    </p></li><li class="listitem"><p><a name="error_er_filsort_abort"></a>
      <a class="indexterm" name="idm46734193102416"></a>

      <a class="indexterm" name="idm46734193101360"></a>

      Error number: <code class="literal">1028</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_filsort_abort"><code class="literal">ER_FILSORT_ABORT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Sort aborted
    </p></li><li class="listitem"><p><a name="error_er_form_not_found"></a>
      <a class="indexterm" name="idm46734193095360"></a>

      <a class="indexterm" name="idm46734193094304"></a>

      Error number: <code class="literal">1029</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_form_not_found"><code class="literal">ER_FORM_NOT_FOUND</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: View '%s' doesn't exist for '%s'
    </p></li><li class="listitem"><p><a name="error_er_get_errno"></a>
      <a class="indexterm" name="idm46734193088288"></a>

      <a class="indexterm" name="idm46734193087248"></a>

      Error number: <code class="literal">1030</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_get_errno"><code class="literal">ER_GET_ERRNO</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Got error %d from storage engine
    </p><p>
      Check the <code class="literal">%d</code> value to see what the OS error
      means. For example, 28 indicates that you have run out of disk
      space.
    </p></li><li class="listitem"><p><a name="error_er_illegal_ha"></a>
      <a class="indexterm" name="idm46734193080144"></a>

      <a class="indexterm" name="idm46734193079088"></a>

      Error number: <code class="literal">1031</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_illegal_ha"><code class="literal">ER_ILLEGAL_HA</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Table storage engine for '%s' doesn't have this option
    </p></li><li class="listitem"><p><a name="error_er_key_not_found"></a>
      <a class="indexterm" name="idm46734193073168"></a>

      <a class="indexterm" name="idm46734193072112"></a>

      Error number: <code class="literal">1032</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_key_not_found"><code class="literal">ER_KEY_NOT_FOUND</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't find record in '%s'
    </p></li><li class="listitem"><p><a name="error_er_not_form_file"></a>
      <a class="indexterm" name="idm46734193066096"></a>

      <a class="indexterm" name="idm46734193065040"></a>

      Error number: <code class="literal">1033</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_not_form_file"><code class="literal">ER_NOT_FORM_FILE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Incorrect information in file: '%s'
    </p></li><li class="listitem"><p><a name="error_er_not_keyfile"></a>
      <a class="indexterm" name="idm46734193059056"></a>

      <a class="indexterm" name="idm46734193058000"></a>

      Error number: <code class="literal">1034</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_not_keyfile"><code class="literal">ER_NOT_KEYFILE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Incorrect key file for table '%s'; try to repair it
    </p></li><li class="listitem"><p><a name="error_er_old_keyfile"></a>
      <a class="indexterm" name="idm46734193052016"></a>

      <a class="indexterm" name="idm46734193050960"></a>

      Error number: <code class="literal">1035</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_old_keyfile"><code class="literal">ER_OLD_KEYFILE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Old key file for table '%s'; repair it!
    </p></li><li class="listitem"><p><a name="error_er_open_as_readonly"></a>
      <a class="indexterm" name="idm46734193044880"></a>

      <a class="indexterm" name="idm46734193043840"></a>

      Error number: <code class="literal">1036</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_open_as_readonly"><code class="literal">ER_OPEN_AS_READONLY</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Table '%s' is read only
    </p></li><li class="listitem"><p><a name="error_er_outofmemory"></a>
      <a class="indexterm" name="idm46734193037856"></a>

      <a class="indexterm" name="idm46734193036800"></a>

      Error number: <code class="literal">1037</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_outofmemory"><code class="literal">ER_OUTOFMEMORY</code></a>; SQLSTATE:
      <code class="literal">HY001</code>
    </p><p>
      Message: Out of memory; restart server and try again (needed %d
      bytes)
    </p></li><li class="listitem"><p><a name="error_er_out_of_sortmemory"></a>
      <a class="indexterm" name="idm46734193030752"></a>

      <a class="indexterm" name="idm46734193029712"></a>

      Error number: <code class="literal">1038</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_out_of_sortmemory"><code class="literal">ER_OUT_OF_SORTMEMORY</code></a>; SQLSTATE:
      <code class="literal">HY001</code>
    </p><p>
      Message: Out of sort memory, consider increasing server sort
      buffer size
    </p></li><li class="listitem"><p><a name="error_er_unexpected_eof"></a>
      <a class="indexterm" name="idm46734193023680"></a>

      <a class="indexterm" name="idm46734193022624"></a>

      Error number: <code class="literal">1039</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unexpected_eof"><code class="literal">ER_UNEXPECTED_EOF</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Unexpected EOF found when reading file '%s' (errno: %d -
      %s)
    </p></li><li class="listitem"><p><a name="error_er_con_count_error"></a>
      <a class="indexterm" name="idm46734193016592"></a>

      <a class="indexterm" name="idm46734193015552"></a>

      Error number: <code class="literal">1040</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_con_count_error"><code class="literal">ER_CON_COUNT_ERROR</code></a>; SQLSTATE:
      <code class="literal">08004</code>
    </p><p>
      Message: Too many connections
    </p></li><li class="listitem"><p><a name="error_er_out_of_resources"></a>
      <a class="indexterm" name="idm46734193009520"></a>

      <a class="indexterm" name="idm46734193008480"></a>

      Error number: <code class="literal">1041</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_out_of_resources"><code class="literal">ER_OUT_OF_RESOURCES</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Out of memory; check if mysqld or some other process uses
      all available memory; if not, you may have to use 'ulimit' to
      allow mysqld to use more memory or you can add more swap space
    </p></li><li class="listitem"><p><a name="error_er_bad_host_error"></a>
      <a class="indexterm" name="idm46734193002336"></a>

      <a class="indexterm" name="idm46734193001280"></a>

      Error number: <code class="literal">1042</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_bad_host_error"><code class="literal">ER_BAD_HOST_ERROR</code></a>; SQLSTATE:
      <code class="literal">08S01</code>
    </p><p>
      Message: Can't get hostname for your address
    </p></li><li class="listitem"><p><a name="error_er_handshake_error"></a>
      <a class="indexterm" name="idm46734192995200"></a>

      <a class="indexterm" name="idm46734192994160"></a>

      Error number: <code class="literal">1043</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_handshake_error"><code class="literal">ER_HANDSHAKE_ERROR</code></a>; SQLSTATE:
      <code class="literal">08S01</code>
    </p><p>
      Message: Bad handshake
    </p></li><li class="listitem"><p><a name="error_er_dbaccess_denied_error"></a>
      <a class="indexterm" name="idm46734192988192"></a>

      <a class="indexterm" name="idm46734192987152"></a>

      Error number: <code class="literal">1044</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_dbaccess_denied_error"><code class="literal">ER_DBACCESS_DENIED_ERROR</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Access denied for user '%s'@'%s' to database '%s'
    </p></li><li class="listitem"><p><a name="error_er_access_denied_error"></a>
      <a class="indexterm" name="idm46734192981248"></a>

      <a class="indexterm" name="idm46734192980208"></a>

      Error number: <code class="literal">1045</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_access_denied_error"><code class="literal">ER_ACCESS_DENIED_ERROR</code></a>; SQLSTATE:
      <code class="literal">28000</code>
    </p><p>
      Message: Access denied for user '%s'@'%s' (using password: %s)
    </p></li><li class="listitem"><p><a name="error_er_no_db_error"></a>
      <a class="indexterm" name="idm46734192974256"></a>

      <a class="indexterm" name="idm46734192973200"></a>

      Error number: <code class="literal">1046</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_db_error"><code class="literal">ER_NO_DB_ERROR</code></a>; SQLSTATE:
      <code class="literal">3D000</code>
    </p><p>
      Message: No database selected
    </p></li><li class="listitem"><p><a name="error_er_unknown_com_error"></a>
      <a class="indexterm" name="idm46734192967184"></a>

      <a class="indexterm" name="idm46734192966144"></a>

      Error number: <code class="literal">1047</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unknown_com_error"><code class="literal">ER_UNKNOWN_COM_ERROR</code></a>; SQLSTATE:
      <code class="literal">08S01</code>
    </p><p>
      Message: Unknown command
    </p></li><li class="listitem"><p><a name="error_er_bad_null_error"></a>
      <a class="indexterm" name="idm46734192960352"></a>

      <a class="indexterm" name="idm46734192959296"></a>

      Error number: <code class="literal">1048</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_bad_null_error"><code class="literal">ER_BAD_NULL_ERROR</code></a>; SQLSTATE:
      <code class="literal">23000</code>
    </p><p>
      Message: Column '%s' cannot be null
    </p></li><li class="listitem"><p><a name="error_er_bad_db_error"></a>
      <a class="indexterm" name="idm46734192953520"></a>

      <a class="indexterm" name="idm46734192952464"></a>

      Error number: <code class="literal">1049</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_bad_db_error"><code class="literal">ER_BAD_DB_ERROR</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Unknown database '%s'
    </p></li><li class="listitem"><p><a name="error_er_table_exists_error"></a>
      <a class="indexterm" name="idm46734192946592"></a>

      <a class="indexterm" name="idm46734192945552"></a>

      Error number: <code class="literal">1050</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_exists_error"><code class="literal">ER_TABLE_EXISTS_ERROR</code></a>; SQLSTATE:
      <code class="literal">42S01</code>
    </p><p>
      Message: Table '%s' already exists
    </p></li><li class="listitem"><p><a name="error_er_bad_table_error"></a>
      <a class="indexterm" name="idm46734192939456"></a>

      <a class="indexterm" name="idm46734192938416"></a>

      Error number: <code class="literal">1051</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_bad_table_error"><code class="literal">ER_BAD_TABLE_ERROR</code></a>; SQLSTATE:
      <code class="literal">42S02</code>
    </p><p>
      Message: Unknown table '%s'
    </p></li><li class="listitem"><p><a name="error_er_non_uniq_error"></a>
      <a class="indexterm" name="idm46734192932448"></a>

      <a class="indexterm" name="idm46734192931392"></a>

      Error number: <code class="literal">1052</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_non_uniq_error"><code class="literal">ER_NON_UNIQ_ERROR</code></a>; SQLSTATE:
      <code class="literal">23000</code>
    </p><p>
      Message: Column '%s' in %s is ambiguous
    </p><pre data-lang="none" class="programlisting">%s = column name
%s = location of column (for example, "field list")</pre><p>
      Likely cause: A column appears in a query without appropriate
      qualification, such as in a select list or ON clause.
    </p><p>
      Examples:
    </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>SELECT i FROM t INNER JOIN t AS t2;</code></strong>
ERROR 1052 (23000): Column 'i' in field list is ambiguous

mysql&gt; <strong class="userinput"><code>SELECT * FROM t LEFT JOIN t AS t2 ON i = i;</code></strong>
ERROR 1052 (23000): Column 'i' in on clause is ambiguous
</pre><p>
      Resolution:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p>
          Qualify the column with the appropriate table name:
        </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>SELECT t2.i FROM t INNER JOIN t AS t2;</code></strong>
</pre></li><li class="listitem"><p>
          Modify the query to avoid the need for qualification:
        </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>SELECT * FROM t LEFT JOIN t AS t2 USING (i);</code></strong>
</pre></li></ul>
</div>
</li><li class="listitem"><p><a name="error_er_server_shutdown"></a>
      <a class="indexterm" name="idm46734192915072"></a>

      <a class="indexterm" name="idm46734192914032"></a>

      Error number: <code class="literal">1053</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_server_shutdown"><code class="literal">ER_SERVER_SHUTDOWN</code></a>; SQLSTATE:
      <code class="literal">08S01</code>
    </p><p>
      Message: Server shutdown in progress
    </p></li><li class="listitem"><p><a name="error_er_bad_field_error"></a>
      <a class="indexterm" name="idm46734192908000"></a>

      <a class="indexterm" name="idm46734192906960"></a>

      Error number: <code class="literal">1054</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_bad_field_error"><code class="literal">ER_BAD_FIELD_ERROR</code></a>; SQLSTATE:
      <code class="literal">42S22</code>
    </p><p>
      Message: Unknown column '%s' in '%s'
    </p></li><li class="listitem"><p><a name="error_er_wrong_field_with_group"></a>
      <a class="indexterm" name="idm46734192900864"></a>

      <a class="indexterm" name="idm46734192899824"></a>

      Error number: <code class="literal">1055</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_field_with_group"><code class="literal">ER_WRONG_FIELD_WITH_GROUP</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: '%s' isn't in GROUP BY
    </p></li><li class="listitem"><p><a name="error_er_wrong_group_field"></a>
      <a class="indexterm" name="idm46734192893760"></a>

      <a class="indexterm" name="idm46734192892720"></a>

      Error number: <code class="literal">1056</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_group_field"><code class="literal">ER_WRONG_GROUP_FIELD</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Can't group on '%s'
    </p></li><li class="listitem"><p><a name="error_er_wrong_sum_select"></a>
      <a class="indexterm" name="idm46734192886624"></a>

      <a class="indexterm" name="idm46734192885584"></a>

      Error number: <code class="literal">1057</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_sum_select"><code class="literal">ER_WRONG_SUM_SELECT</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Statement has sum functions and columns in same statement
    </p></li><li class="listitem"><p><a name="error_er_wrong_value_count"></a>
      <a class="indexterm" name="idm46734192879456"></a>

      <a class="indexterm" name="idm46734192878416"></a>

      Error number: <code class="literal">1058</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_value_count"><code class="literal">ER_WRONG_VALUE_COUNT</code></a>; SQLSTATE:
      <code class="literal">21S01</code>
    </p><p>
      Message: Column count doesn't match value count
    </p></li><li class="listitem"><p><a name="error_er_too_long_ident"></a>
      <a class="indexterm" name="idm46734192872416"></a>

      <a class="indexterm" name="idm46734192871360"></a>

      Error number: <code class="literal">1059</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_long_ident"><code class="literal">ER_TOO_LONG_IDENT</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Identifier name '%s' is too long
    </p></li><li class="listitem"><p><a name="error_er_dup_fieldname"></a>
      <a class="indexterm" name="idm46734192865344"></a>

      <a class="indexterm" name="idm46734192864288"></a>

      Error number: <code class="literal">1060</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_dup_fieldname"><code class="literal">ER_DUP_FIELDNAME</code></a>; SQLSTATE:
      <code class="literal">42S21</code>
    </p><p>
      Message: Duplicate column name '%s'
    </p></li><li class="listitem"><p><a name="error_er_dup_keyname"></a>
      <a class="indexterm" name="idm46734192858336"></a>

      <a class="indexterm" name="idm46734192857280"></a>

      Error number: <code class="literal">1061</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_dup_keyname"><code class="literal">ER_DUP_KEYNAME</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Duplicate key name '%s'
    </p></li><li class="listitem"><p><a name="error_er_dup_entry"></a>
      <a class="indexterm" name="idm46734192851376"></a>

      <a class="indexterm" name="idm46734192850336"></a>

      Error number: <code class="literal">1062</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_dup_entry"><code class="literal">ER_DUP_ENTRY</code></a>; SQLSTATE:
      <code class="literal">23000</code>
    </p><p>
      Message: Duplicate entry '%s' for key %d
    </p><p>
      The message returned with this error uses the format string for
      <a class="link" href="error-handling.html#error_er_dup_entry_with_key_name"><code class="literal">ER_DUP_ENTRY_WITH_KEY_NAME</code></a>.
    </p></li><li class="listitem"><p><a name="error_er_wrong_field_spec"></a>
      <a class="indexterm" name="idm46734192842704"></a>

      <a class="indexterm" name="idm46734192841664"></a>

      Error number: <code class="literal">1063</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_field_spec"><code class="literal">ER_WRONG_FIELD_SPEC</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Incorrect column specifier for column '%s'
    </p></li><li class="listitem"><p><a name="error_er_parse_error"></a>
      <a class="indexterm" name="idm46734192835664"></a>

      <a class="indexterm" name="idm46734192834608"></a>

      Error number: <code class="literal">1064</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_parse_error"><code class="literal">ER_PARSE_ERROR</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: %s near '%s' at line %d
    </p></li><li class="listitem"><p><a name="error_er_empty_query"></a>
      <a class="indexterm" name="idm46734192828656"></a>

      <a class="indexterm" name="idm46734192827600"></a>

      Error number: <code class="literal">1065</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_empty_query"><code class="literal">ER_EMPTY_QUERY</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Query was empty
    </p></li><li class="listitem"><p><a name="error_er_nonuniq_table"></a>
      <a class="indexterm" name="idm46734192821648"></a>

      <a class="indexterm" name="idm46734192820592"></a>

      Error number: <code class="literal">1066</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_nonuniq_table"><code class="literal">ER_NONUNIQ_TABLE</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Not unique table/alias: '%s'
    </p></li><li class="listitem"><p><a name="error_er_invalid_default"></a>
      <a class="indexterm" name="idm46734192814528"></a>

      <a class="indexterm" name="idm46734192813488"></a>

      Error number: <code class="literal">1067</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_default"><code class="literal">ER_INVALID_DEFAULT</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Invalid default value for '%s'
    </p></li><li class="listitem"><p><a name="error_er_multiple_pri_key"></a>
      <a class="indexterm" name="idm46734192807392"></a>

      <a class="indexterm" name="idm46734192806352"></a>

      Error number: <code class="literal">1068</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_multiple_pri_key"><code class="literal">ER_MULTIPLE_PRI_KEY</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Multiple primary key defined
    </p></li><li class="listitem"><p><a name="error_er_too_many_keys"></a>
      <a class="indexterm" name="idm46734192800304"></a>

      <a class="indexterm" name="idm46734192799248"></a>

      Error number: <code class="literal">1069</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_many_keys"><code class="literal">ER_TOO_MANY_KEYS</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Too many keys specified; max %d keys allowed
    </p></li><li class="listitem"><p><a name="error_er_too_many_key_parts"></a>
      <a class="indexterm" name="idm46734192793232"></a>

      <a class="indexterm" name="idm46734192792192"></a>

      Error number: <code class="literal">1070</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_many_key_parts"><code class="literal">ER_TOO_MANY_KEY_PARTS</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Too many key parts specified; max %d parts allowed
    </p></li><li class="listitem"><p><a name="error_er_too_long_key"></a>
      <a class="indexterm" name="idm46734192786192"></a>

      <a class="indexterm" name="idm46734192785184"></a>

      Error number: <code class="literal">1071</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_long_key"><code class="literal">ER_TOO_LONG_KEY</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Specified key was too long; max key length is %d bytes
    </p></li><li class="listitem"><p><a name="error_er_key_column_does_not_exits"></a>
      <a class="indexterm" name="idm46734192779216"></a>

      <a class="indexterm" name="idm46734192778176"></a>

      Error number: <code class="literal">1072</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_key_column_does_not_exits"><code class="literal">ER_KEY_COLUMN_DOES_NOT_EXITS</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Key column '%s' doesn't exist in table
    </p></li><li class="listitem"><p><a name="error_er_blob_used_as_key"></a>
      <a class="indexterm" name="idm46734192772032"></a>

      <a class="indexterm" name="idm46734192770992"></a>

      Error number: <code class="literal">1073</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_blob_used_as_key"><code class="literal">ER_BLOB_USED_AS_KEY</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: BLOB column '%s' can't be used in key specification with
      the used table type
    </p></li><li class="listitem"><p><a name="error_er_too_big_fieldlength"></a>
      <a class="indexterm" name="idm46734192764912"></a>

      <a class="indexterm" name="idm46734192763872"></a>

      Error number: <code class="literal">1074</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_big_fieldlength"><code class="literal">ER_TOO_BIG_FIELDLENGTH</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Column length too big for column '%s' (max = %lu); use
      BLOB or TEXT instead
    </p></li><li class="listitem"><p><a name="error_er_wrong_auto_key"></a>
      <a class="indexterm" name="idm46734192757840"></a>

      <a class="indexterm" name="idm46734192756784"></a>

      Error number: <code class="literal">1075</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_auto_key"><code class="literal">ER_WRONG_AUTO_KEY</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Incorrect table definition; there can be only one auto
      column and it must be defined as a key
    </p></li><li class="listitem"><p><a name="error_er_ready"></a>
      <a class="indexterm" name="idm46734192750752"></a>

      <a class="indexterm" name="idm46734192749712"></a>

      Error number: <code class="literal">1076</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_ready"><code class="literal">ER_READY</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: %s: ready for connections. Version: '%s' socket: '%s'
      port: %d
    </p></li><li class="listitem"><p><a name="error_er_normal_shutdown"></a>
      <a class="indexterm" name="idm46734192743600"></a>

      <a class="indexterm" name="idm46734192742560"></a>

      Error number: <code class="literal">1077</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_normal_shutdown"><code class="literal">ER_NORMAL_SHUTDOWN</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: %s: Normal shutdown
    </p></li><li class="listitem"><p><a name="error_er_got_signal"></a>
      <a class="indexterm" name="idm46734192736512"></a>

      <a class="indexterm" name="idm46734192735456"></a>

      Error number: <code class="literal">1078</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_got_signal"><code class="literal">ER_GOT_SIGNAL</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: %s: Got signal %d. Aborting!
    </p></li><li class="listitem"><p><a name="error_er_shutdown_complete"></a>
      <a class="indexterm" name="idm46734192729456"></a>

      <a class="indexterm" name="idm46734192728416"></a>

      Error number: <code class="literal">1079</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_shutdown_complete"><code class="literal">ER_SHUTDOWN_COMPLETE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: %s: Shutdown complete
    </p></li><li class="listitem"><p><a name="error_er_forcing_close"></a>
      <a class="indexterm" name="idm46734192722432"></a>

      <a class="indexterm" name="idm46734192721376"></a>

      Error number: <code class="literal">1080</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_forcing_close"><code class="literal">ER_FORCING_CLOSE</code></a>; SQLSTATE:
      <code class="literal">08S01</code>
    </p><p>
      Message: %s: Forcing close of thread %ld user: '%s'
    </p></li><li class="listitem"><p><a name="error_er_ipsock_error"></a>
      <a class="indexterm" name="idm46734192715344"></a>

      <a class="indexterm" name="idm46734192714288"></a>

      Error number: <code class="literal">1081</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_ipsock_error"><code class="literal">ER_IPSOCK_ERROR</code></a>; SQLSTATE:
      <code class="literal">08S01</code>
    </p><p>
      Message: Can't create IP socket
    </p></li><li class="listitem"><p><a name="error_er_no_such_index"></a>
      <a class="indexterm" name="idm46734192708336"></a>

      <a class="indexterm" name="idm46734192707280"></a>

      Error number: <code class="literal">1082</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_such_index"><code class="literal">ER_NO_SUCH_INDEX</code></a>; SQLSTATE:
      <code class="literal">42S12</code>
    </p><p>
      Message: Table '%s' has no index like the one used in CREATE
      INDEX; recreate the table
    </p></li><li class="listitem"><p><a name="error_er_wrong_field_terminators"></a>
      <a class="indexterm" name="idm46734192701280"></a>

      <a class="indexterm" name="idm46734192700240"></a>

      Error number: <code class="literal">1083</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_field_terminators"><code class="literal">ER_WRONG_FIELD_TERMINATORS</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Field separator argument is not what is expected; check
      the manual
    </p></li><li class="listitem"><p><a name="error_er_blobs_and_no_terminated"></a>
      <a class="indexterm" name="idm46734192694064"></a>

      <a class="indexterm" name="idm46734192693024"></a>

      Error number: <code class="literal">1084</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_blobs_and_no_terminated"><code class="literal">ER_BLOBS_AND_NO_TERMINATED</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: You can't use fixed rowlength with BLOBs; please use
      'fields terminated by'
    </p></li><li class="listitem"><p><a name="error_er_textfile_not_readable"></a>
      <a class="indexterm" name="idm46734192686912"></a>

      <a class="indexterm" name="idm46734192685872"></a>

      Error number: <code class="literal">1085</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_textfile_not_readable"><code class="literal">ER_TEXTFILE_NOT_READABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The file '%s' must be in the database directory or be
      readable by all
    </p></li><li class="listitem"><p><a name="error_er_file_exists_error"></a>
      <a class="indexterm" name="idm46734192679760"></a>

      <a class="indexterm" name="idm46734192678720"></a>

      Error number: <code class="literal">1086</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_file_exists_error"><code class="literal">ER_FILE_EXISTS_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: File '%s' already exists
    </p></li><li class="listitem"><p><a name="error_er_load_info"></a>
      <a class="indexterm" name="idm46734192672736"></a>

      <a class="indexterm" name="idm46734192671696"></a>

      Error number: <code class="literal">1087</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_load_info"><code class="literal">ER_LOAD_INFO</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Records: %ld Deleted: %ld Skipped: %ld Warnings: %ld
    </p></li><li class="listitem"><p><a name="error_er_alter_info"></a>
      <a class="indexterm" name="idm46734192665712"></a>

      <a class="indexterm" name="idm46734192664656"></a>

      Error number: <code class="literal">1088</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_alter_info"><code class="literal">ER_ALTER_INFO</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Records: %ld Duplicates: %ld
    </p></li><li class="listitem"><p><a name="error_er_wrong_sub_key"></a>
      <a class="indexterm" name="idm46734192658704"></a>

      <a class="indexterm" name="idm46734192657648"></a>

      Error number: <code class="literal">1089</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_sub_key"><code class="literal">ER_WRONG_SUB_KEY</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Incorrect prefix key; the used key part isn't a string,
      the used length is longer than the key part, or the storage engine
      doesn't support unique prefix keys
    </p></li><li class="listitem"><p><a name="error_er_cant_remove_all_fields"></a>
      <a class="indexterm" name="idm46734192651504"></a>

      <a class="indexterm" name="idm46734192650464"></a>

      Error number: <code class="literal">1090</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_remove_all_fields"><code class="literal">ER_CANT_REMOVE_ALL_FIELDS</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: You can't delete all columns with ALTER TABLE; use DROP
      TABLE instead
    </p></li><li class="listitem"><p><a name="error_er_cant_drop_field_or_key"></a>
      <a class="indexterm" name="idm46734192644352"></a>

      <a class="indexterm" name="idm46734192643312"></a>

      Error number: <code class="literal">1091</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_drop_field_or_key"><code class="literal">ER_CANT_DROP_FIELD_OR_KEY</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Can't DROP '%s'; check that column/key exists
    </p></li><li class="listitem"><p><a name="error_er_insert_info"></a>
      <a class="indexterm" name="idm46734192637280"></a>

      <a class="indexterm" name="idm46734192636224"></a>

      Error number: <code class="literal">1092</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_insert_info"><code class="literal">ER_INSERT_INFO</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Records: %ld Duplicates: %ld Warnings: %ld
    </p></li><li class="listitem"><p><a name="error_er_update_table_used"></a>
      <a class="indexterm" name="idm46734192630256"></a>

      <a class="indexterm" name="idm46734192629216"></a>

      Error number: <code class="literal">1093</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_update_table_used"><code class="literal">ER_UPDATE_TABLE_USED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: You can't specify target table '%s' for update in FROM
      clause
    </p><p>
      This error occurs for attempts to select from and modify the same
      table within a single statement. If the select attempt occurs
      within a derived table, you can avoid this error by setting the
      <code class="literal">derived_merge</code> flag of the
      <a class="link" href="server-administration.html#sysvar_optimizer_switch"><code class="literal">optimizer_switch</code></a> system variable
      to force the subquery to be materialized into a temporary table,
      which effectively causes it to be a different table from the one
      modified. See <a class="xref" href="optimization.html#derived-table-optimization" title="8.2.2.4 Optimizing Derived Tables and View References with Merging or Materialization">Section 8.2.2.4, “Optimizing Derived Tables and View References with Merging or
          Materialization”</a>.
    </p></li><li class="listitem"><p><a name="error_er_no_such_thread"></a>
      <a class="indexterm" name="idm46734192619872"></a>

      <a class="indexterm" name="idm46734192618816"></a>

      Error number: <code class="literal">1094</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_such_thread"><code class="literal">ER_NO_SUCH_THREAD</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Unknown thread id: %lu
    </p></li><li class="listitem"><p><a name="error_er_kill_denied_error"></a>
      <a class="indexterm" name="idm46734192612816"></a>

      <a class="indexterm" name="idm46734192611776"></a>

      Error number: <code class="literal">1095</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_kill_denied_error"><code class="literal">ER_KILL_DENIED_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: You are not owner of thread %lu
    </p></li><li class="listitem"><p><a name="error_er_no_tables_used"></a>
      <a class="indexterm" name="idm46734192605792"></a>

      <a class="indexterm" name="idm46734192604736"></a>

      Error number: <code class="literal">1096</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_tables_used"><code class="literal">ER_NO_TABLES_USED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: No tables used
    </p></li><li class="listitem"><p><a name="error_er_too_big_set"></a>
      <a class="indexterm" name="idm46734192598800"></a>

      <a class="indexterm" name="idm46734192597744"></a>

      Error number: <code class="literal">1097</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_big_set"><code class="literal">ER_TOO_BIG_SET</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Too many strings for column %s and SET
    </p></li><li class="listitem"><p><a name="error_er_no_unique_logfile"></a>
      <a class="indexterm" name="idm46734192591728"></a>

      <a class="indexterm" name="idm46734192590688"></a>

      Error number: <code class="literal">1098</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_unique_logfile"><code class="literal">ER_NO_UNIQUE_LOGFILE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't generate a unique log-filename %s.(1-999)
    </p></li><li class="listitem"><p><a name="error_er_table_not_locked_for_write"></a>
      <a class="indexterm" name="idm46734192584640"></a>

      <a class="indexterm" name="idm46734192583536"></a>

      Error number: <code class="literal">1099</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_not_locked_for_write"><code class="literal">ER_TABLE_NOT_LOCKED_FOR_WRITE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Table '%s' was locked with a READ lock and can't be
      updated
    </p></li><li class="listitem"><p><a name="error_er_table_not_locked"></a>
      <a class="indexterm" name="idm46734192577488"></a>

      <a class="indexterm" name="idm46734192576448"></a>

      Error number: <code class="literal">1100</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_not_locked"><code class="literal">ER_TABLE_NOT_LOCKED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Table '%s' was not locked with LOCK TABLES
    </p></li><li class="listitem"><p><a name="error_er_blob_cant_have_default"></a>
      <a class="indexterm" name="idm46734192570400"></a>

      <a class="indexterm" name="idm46734192569360"></a>

      Error number: <code class="literal">1101</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_blob_cant_have_default"><code class="literal">ER_BLOB_CANT_HAVE_DEFAULT</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: BLOB, TEXT, GEOMETRY or JSON column '%s' can't have a
      default value
    </p></li><li class="listitem"><p><a name="error_er_wrong_db_name"></a>
      <a class="indexterm" name="idm46734192563280"></a>

      <a class="indexterm" name="idm46734192562224"></a>

      Error number: <code class="literal">1102</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_db_name"><code class="literal">ER_WRONG_DB_NAME</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Incorrect database name '%s'
    </p></li><li class="listitem"><p><a name="error_er_wrong_table_name"></a>
      <a class="indexterm" name="idm46734192556352"></a>

      <a class="indexterm" name="idm46734192555312"></a>

      Error number: <code class="literal">1103</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_table_name"><code class="literal">ER_WRONG_TABLE_NAME</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Incorrect table name '%s'
    </p></li><li class="listitem"><p><a name="error_er_too_big_select"></a>
      <a class="indexterm" name="idm46734192549264"></a>

      <a class="indexterm" name="idm46734192548208"></a>

      Error number: <code class="literal">1104</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_big_select"><code class="literal">ER_TOO_BIG_SELECT</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: The SELECT would examine more than MAX_JOIN_SIZE rows;
      check your WHERE and use SET SQL_BIG_SELECTS=1 or SET
      MAX_JOIN_SIZE=# if the SELECT is okay
    </p></li><li class="listitem"><p><a name="error_er_unknown_error"></a>
      <a class="indexterm" name="idm46734192542128"></a>

      <a class="indexterm" name="idm46734192541072"></a>

      Error number: <code class="literal">1105</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unknown_error"><code class="literal">ER_UNKNOWN_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Unknown error
    </p></li><li class="listitem"><p><a name="error_er_unknown_procedure"></a>
      <a class="indexterm" name="idm46734192535152"></a>

      <a class="indexterm" name="idm46734192534112"></a>

      Error number: <code class="literal">1106</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unknown_procedure"><code class="literal">ER_UNKNOWN_PROCEDURE</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Unknown procedure '%s'
    </p></li><li class="listitem"><p><a name="error_er_wrong_paramcount_to_procedure"></a>
      <a class="indexterm" name="idm46734192528016"></a>

      <a class="indexterm" name="idm46734192526912"></a>

      Error number: <code class="literal">1107</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_paramcount_to_procedure"><code class="literal">ER_WRONG_PARAMCOUNT_TO_PROCEDURE</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Incorrect parameter count to procedure '%s'
    </p></li><li class="listitem"><p><a name="error_er_wrong_parameters_to_procedure"></a>
      <a class="indexterm" name="idm46734192520816"></a>

      <a class="indexterm" name="idm46734192519712"></a>

      Error number: <code class="literal">1108</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_parameters_to_procedure"><code class="literal">ER_WRONG_PARAMETERS_TO_PROCEDURE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Incorrect parameters to procedure '%s'
    </p></li><li class="listitem"><p><a name="error_er_unknown_table"></a>
      <a class="indexterm" name="idm46734192513728"></a>

      <a class="indexterm" name="idm46734192512672"></a>

      Error number: <code class="literal">1109</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unknown_table"><code class="literal">ER_UNKNOWN_TABLE</code></a>; SQLSTATE:
      <code class="literal">42S02</code>
    </p><p>
      Message: Unknown table '%s' in %s
    </p></li><li class="listitem"><p><a name="error_er_field_specified_twice"></a>
      <a class="indexterm" name="idm46734192506672"></a>

      <a class="indexterm" name="idm46734192505632"></a>

      Error number: <code class="literal">1110</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_field_specified_twice"><code class="literal">ER_FIELD_SPECIFIED_TWICE</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Column '%s' specified twice
    </p></li><li class="listitem"><p><a name="error_er_invalid_group_func_use"></a>
      <a class="indexterm" name="idm46734192499616"></a>

      <a class="indexterm" name="idm46734192498576"></a>

      Error number: <code class="literal">1111</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_group_func_use"><code class="literal">ER_INVALID_GROUP_FUNC_USE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Invalid use of group function
    </p></li><li class="listitem"><p><a name="error_er_unsupported_extension"></a>
      <a class="indexterm" name="idm46734192492576"></a>

      <a class="indexterm" name="idm46734192491536"></a>

      Error number: <code class="literal">1112</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unsupported_extension"><code class="literal">ER_UNSUPPORTED_EXTENSION</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Table '%s' uses an extension that doesn't exist in this
      MySQL version
    </p></li><li class="listitem"><p><a name="error_er_table_must_have_columns"></a>
      <a class="indexterm" name="idm46734192485536"></a>

      <a class="indexterm" name="idm46734192484496"></a>

      Error number: <code class="literal">1113</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_must_have_columns"><code class="literal">ER_TABLE_MUST_HAVE_COLUMNS</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: A table must have at least 1 column
    </p></li><li class="listitem"><p><a name="error_er_record_file_full"></a>
      <a class="indexterm" name="idm46734192478416"></a>

      <a class="indexterm" name="idm46734192477376"></a>

      Error number: <code class="literal">1114</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_record_file_full"><code class="literal">ER_RECORD_FILE_FULL</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The table '%s' is full
    </p><p>
      <code class="literal">InnoDB</code> reports this error when the system
      tablespace runs out of free space. Reconfigure the system
      tablespace to add a new data file.
    </p></li><li class="listitem"><p><a name="error_er_unknown_character_set"></a>
      <a class="indexterm" name="idm46734192470048"></a>

      <a class="indexterm" name="idm46734192469008"></a>

      Error number: <code class="literal">1115</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unknown_character_set"><code class="literal">ER_UNKNOWN_CHARACTER_SET</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Unknown character set: '%s'
    </p></li><li class="listitem"><p><a name="error_er_too_many_tables"></a>
      <a class="indexterm" name="idm46734192462944"></a>

      <a class="indexterm" name="idm46734192461904"></a>

      Error number: <code class="literal">1116</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_many_tables"><code class="literal">ER_TOO_MANY_TABLES</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Too many tables; MySQL can only use %d tables in a join
    </p></li><li class="listitem"><p><a name="error_er_too_many_fields"></a>
      <a class="indexterm" name="idm46734192455840"></a>

      <a class="indexterm" name="idm46734192454800"></a>

      Error number: <code class="literal">1117</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_many_fields"><code class="literal">ER_TOO_MANY_FIELDS</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Too many columns
    </p></li><li class="listitem"><p><a name="error_er_too_big_rowsize"></a>
      <a class="indexterm" name="idm46734192448720"></a>

      <a class="indexterm" name="idm46734192447680"></a>

      Error number: <code class="literal">1118</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_big_rowsize"><code class="literal">ER_TOO_BIG_ROWSIZE</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Row size too large. The maximum row size for the used
      table type, not counting BLOBs, is %ld. This includes storage
      overhead, check the manual. You have to change some columns to
      TEXT or BLOBs
    </p></li><li class="listitem"><p><a name="error_er_stack_overrun"></a>
      <a class="indexterm" name="idm46734192441584"></a>

      <a class="indexterm" name="idm46734192440528"></a>

      Error number: <code class="literal">1119</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_stack_overrun"><code class="literal">ER_STACK_OVERRUN</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Thread stack overrun: Used: %ld of a %ld stack. Use
      'mysqld --thread_stack=#' to specify a bigger stack if needed
    </p></li><li class="listitem"><p><a name="error_er_wrong_outer_join"></a>
      <a class="indexterm" name="idm46734192434432"></a>

      <a class="indexterm" name="idm46734192433392"></a>

      Error number: <code class="literal">1120</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_outer_join"><code class="literal">ER_WRONG_OUTER_JOIN</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Cross dependency found in OUTER JOIN; examine your ON
      conditions
    </p></li><li class="listitem"><p><a name="error_er_null_column_in_index"></a>
      <a class="indexterm" name="idm46734192427248"></a>

      <a class="indexterm" name="idm46734192426208"></a>

      Error number: <code class="literal">1121</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_null_column_in_index"><code class="literal">ER_NULL_COLUMN_IN_INDEX</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Table handler doesn't support NULL in given index. Please
      change column '%s' to be NOT NULL or use another handler
    </p></li><li class="listitem"><p><a name="error_er_cant_find_udf"></a>
      <a class="indexterm" name="idm46734192420064"></a>

      <a class="indexterm" name="idm46734192419008"></a>

      Error number: <code class="literal">1122</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_find_udf"><code class="literal">ER_CANT_FIND_UDF</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't load function '%s'
    </p></li><li class="listitem"><p><a name="error_er_cant_initialize_udf"></a>
      <a class="indexterm" name="idm46734192412944"></a>

      <a class="indexterm" name="idm46734192411904"></a>

      Error number: <code class="literal">1123</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_initialize_udf"><code class="literal">ER_CANT_INITIALIZE_UDF</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't initialize function '%s'; %s
    </p></li><li class="listitem"><p><a name="error_er_udf_no_paths"></a>
      <a class="indexterm" name="idm46734192405920"></a>

      <a class="indexterm" name="idm46734192404864"></a>

      Error number: <code class="literal">1124</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_udf_no_paths"><code class="literal">ER_UDF_NO_PATHS</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: No paths allowed for shared library
    </p></li><li class="listitem"><p><a name="error_er_udf_exists"></a>
      <a class="indexterm" name="idm46734192398832"></a>

      <a class="indexterm" name="idm46734192397776"></a>

      Error number: <code class="literal">1125</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_udf_exists"><code class="literal">ER_UDF_EXISTS</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Function '%s' already exists
    </p></li><li class="listitem"><p><a name="error_er_cant_open_library"></a>
      <a class="indexterm" name="idm46734192391776"></a>

      <a class="indexterm" name="idm46734192390736"></a>

      Error number: <code class="literal">1126</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_open_library"><code class="literal">ER_CANT_OPEN_LIBRARY</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't open shared library '%s' (errno: %d %s)
    </p></li><li class="listitem"><p><a name="error_er_cant_find_dl_entry"></a>
      <a class="indexterm" name="idm46734192384736"></a>

      <a class="indexterm" name="idm46734192383696"></a>

      Error number: <code class="literal">1127</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_find_dl_entry"><code class="literal">ER_CANT_FIND_DL_ENTRY</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't find symbol '%s' in library
    </p></li><li class="listitem"><p><a name="error_er_function_not_defined"></a>
      <a class="indexterm" name="idm46734192377664"></a>

      <a class="indexterm" name="idm46734192376624"></a>

      Error number: <code class="literal">1128</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_function_not_defined"><code class="literal">ER_FUNCTION_NOT_DEFINED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Function '%s' is not defined
    </p></li><li class="listitem"><p><a name="error_er_host_is_blocked"></a>
      <a class="indexterm" name="idm46734192370528"></a>

      <a class="indexterm" name="idm46734192369488"></a>

      Error number: <code class="literal">1129</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_host_is_blocked"><code class="literal">ER_HOST_IS_BLOCKED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Host '%s' is blocked because of many connection errors;
      unblock with 'mysqladmin flush-hosts'
    </p></li><li class="listitem"><p><a name="error_er_host_not_privileged"></a>
      <a class="indexterm" name="idm46734192363424"></a>

      <a class="indexterm" name="idm46734192362384"></a>

      Error number: <code class="literal">1130</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_host_not_privileged"><code class="literal">ER_HOST_NOT_PRIVILEGED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Host '%s' is not allowed to connect to this MySQL server
    </p></li><li class="listitem"><p><a name="error_er_password_anonymous_user"></a>
      <a class="indexterm" name="idm46734192356448"></a>

      <a class="indexterm" name="idm46734192355408"></a>

      Error number: <code class="literal">1131</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_password_anonymous_user"><code class="literal">ER_PASSWORD_ANONYMOUS_USER</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: You are using MySQL as an anonymous user and anonymous
      users are not allowed to change passwords
    </p></li><li class="listitem"><p><a name="error_er_password_not_allowed"></a>
      <a class="indexterm" name="idm46734192349264"></a>

      <a class="indexterm" name="idm46734192348224"></a>

      Error number: <code class="literal">1132</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_password_not_allowed"><code class="literal">ER_PASSWORD_NOT_ALLOWED</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: You must have privileges to update tables in the mysql
      database to be able to change passwords for others
    </p></li><li class="listitem"><p><a name="error_er_password_no_match"></a>
      <a class="indexterm" name="idm46734192342048"></a>

      <a class="indexterm" name="idm46734192341008"></a>

      Error number: <code class="literal">1133</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_password_no_match"><code class="literal">ER_PASSWORD_NO_MATCH</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Can't find any matching row in the user table
    </p></li><li class="listitem"><p><a name="error_er_update_info"></a>
      <a class="indexterm" name="idm46734192335008"></a>

      <a class="indexterm" name="idm46734192333952"></a>

      Error number: <code class="literal">1134</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_update_info"><code class="literal">ER_UPDATE_INFO</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Rows matched: %ld Changed: %ld Warnings: %ld
    </p></li><li class="listitem"><p><a name="error_er_cant_create_thread"></a>
      <a class="indexterm" name="idm46734192327936"></a>

      <a class="indexterm" name="idm46734192326896"></a>

      Error number: <code class="literal">1135</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_create_thread"><code class="literal">ER_CANT_CREATE_THREAD</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't create a new thread (errno %d); if you are not out
      of available memory, you can consult the manual for a possible
      OS-dependent bug
    </p></li><li class="listitem"><p><a name="error_er_wrong_value_count_on_row"></a>
      <a class="indexterm" name="idm46734192320736"></a>

      <a class="indexterm" name="idm46734192319696"></a>

      Error number: <code class="literal">1136</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_value_count_on_row"><code class="literal">ER_WRONG_VALUE_COUNT_ON_ROW</code></a>;
      SQLSTATE: <code class="literal">21S01</code>
    </p><p>
      Message: Column count doesn't match value count at row %ld
    </p></li><li class="listitem"><p><a name="error_er_cant_reopen_table"></a>
      <a class="indexterm" name="idm46734192313616"></a>

      <a class="indexterm" name="idm46734192312576"></a>

      Error number: <code class="literal">1137</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_reopen_table"><code class="literal">ER_CANT_REOPEN_TABLE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't reopen table: '%s'
    </p></li><li class="listitem"><p><a name="error_er_invalid_use_of_null"></a>
      <a class="indexterm" name="idm46734192306544"></a>

      <a class="indexterm" name="idm46734192305504"></a>

      Error number: <code class="literal">1138</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_use_of_null"><code class="literal">ER_INVALID_USE_OF_NULL</code></a>; SQLSTATE:
      <code class="literal">22004</code>
    </p><p>
      Message: Invalid use of NULL value
    </p></li><li class="listitem"><p><a name="error_er_regexp_error"></a>
      <a class="indexterm" name="idm46734192299520"></a>

      <a class="indexterm" name="idm46734192298464"></a>

      Error number: <code class="literal">1139</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_regexp_error"><code class="literal">ER_REGEXP_ERROR</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Got error '%s' from regexp
    </p></li><li class="listitem"><p><a name="error_er_mix_of_group_func_and_fields"></a>
      <a class="indexterm" name="idm46734192292464"></a>

      <a class="indexterm" name="idm46734192291360"></a>

      Error number: <code class="literal">1140</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_mix_of_group_func_and_fields"><code class="literal">ER_MIX_OF_GROUP_FUNC_AND_FIELDS</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no
      GROUP columns is illegal if there is no GROUP BY clause
    </p></li><li class="listitem"><p><a name="error_er_nonexisting_grant"></a>
      <a class="indexterm" name="idm46734192285248"></a>

      <a class="indexterm" name="idm46734192284208"></a>

      Error number: <code class="literal">1141</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_nonexisting_grant"><code class="literal">ER_NONEXISTING_GRANT</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: There is no such grant defined for user '%s' on host '%s'
    </p></li><li class="listitem"><p><a name="error_er_tableaccess_denied_error"></a>
      <a class="indexterm" name="idm46734192278080"></a>

      <a class="indexterm" name="idm46734192277040"></a>

      Error number: <code class="literal">1142</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_tableaccess_denied_error"><code class="literal">ER_TABLEACCESS_DENIED_ERROR</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: %s command denied to user '%s'@'%s' for table '%s'
    </p></li><li class="listitem"><p><a name="error_er_columnaccess_denied_error"></a>
      <a class="indexterm" name="idm46734192270896"></a>

      <a class="indexterm" name="idm46734192269856"></a>

      Error number: <code class="literal">1143</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_columnaccess_denied_error"><code class="literal">ER_COLUMNACCESS_DENIED_ERROR</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: %s command denied to user '%s'@'%s' for column '%s' in
      table '%s'
    </p></li><li class="listitem"><p><a name="error_er_illegal_grant_for_table"></a>
      <a class="indexterm" name="idm46734192263744"></a>

      <a class="indexterm" name="idm46734192262704"></a>

      Error number: <code class="literal">1144</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_illegal_grant_for_table"><code class="literal">ER_ILLEGAL_GRANT_FOR_TABLE</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Illegal GRANT/REVOKE command; please consult the manual
      to see which privileges can be used
    </p></li><li class="listitem"><p><a name="error_er_grant_wrong_host_or_user"></a>
      <a class="indexterm" name="idm46734192256512"></a>

      <a class="indexterm" name="idm46734192255472"></a>

      Error number: <code class="literal">1145</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_grant_wrong_host_or_user"><code class="literal">ER_GRANT_WRONG_HOST_OR_USER</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: The host or user argument to GRANT is too long
    </p></li><li class="listitem"><p><a name="error_er_no_such_table"></a>
      <a class="indexterm" name="idm46734192249424"></a>

      <a class="indexterm" name="idm46734192248368"></a>

      Error number: <code class="literal">1146</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_such_table"><code class="literal">ER_NO_SUCH_TABLE</code></a>; SQLSTATE:
      <code class="literal">42S02</code>
    </p><p>
      Message: Table '%s.%s' doesn't exist
    </p></li><li class="listitem"><p><a name="error_er_nonexisting_table_grant"></a>
      <a class="indexterm" name="idm46734192242496"></a>

      <a class="indexterm" name="idm46734192241456"></a>

      Error number: <code class="literal">1147</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_nonexisting_table_grant"><code class="literal">ER_NONEXISTING_TABLE_GRANT</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: There is no such grant defined for user '%s' on host '%s'
      on table '%s'
    </p></li><li class="listitem"><p><a name="error_er_not_allowed_command"></a>
      <a class="indexterm" name="idm46734192235392"></a>

      <a class="indexterm" name="idm46734192234352"></a>

      Error number: <code class="literal">1148</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_not_allowed_command"><code class="literal">ER_NOT_ALLOWED_COMMAND</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: The used command is not allowed with this MySQL version
    </p></li><li class="listitem"><p><a name="error_er_syntax_error"></a>
      <a class="indexterm" name="idm46734192228336"></a>

      <a class="indexterm" name="idm46734192227280"></a>

      Error number: <code class="literal">1149</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_syntax_error"><code class="literal">ER_SYNTAX_ERROR</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: You have an error in your SQL syntax; check the manual
      that corresponds to your MySQL server version for the right syntax
      to use
    </p></li><li class="listitem"><p><a name="error_er_unused1"></a>
      <a class="indexterm" name="idm46734192221216"></a>

      <a class="indexterm" name="idm46734192220176"></a>

      Error number: <code class="literal">1150</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unused1"><code class="literal">ER_UNUSED1</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Delayed insert thread couldn't get requested lock for
      table %s
    </p></li><li class="listitem"><p><a name="error_er_unused2"></a>
      <a class="indexterm" name="idm46734192214176"></a>

      <a class="indexterm" name="idm46734192213136"></a>

      Error number: <code class="literal">1151</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unused2"><code class="literal">ER_UNUSED2</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Too many delayed threads in use
    </p></li><li class="listitem"><p><a name="error_er_aborting_connection"></a>
      <a class="indexterm" name="idm46734192207136"></a>

      <a class="indexterm" name="idm46734192206096"></a>

      Error number: <code class="literal">1152</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_aborting_connection"><code class="literal">ER_ABORTING_CONNECTION</code></a>; SQLSTATE:
      <code class="literal">08S01</code>
    </p><p>
      Message: Aborted connection %ld to db: '%s' user: '%s' (%s)
    </p></li><li class="listitem"><p><a name="error_er_net_packet_too_large"></a>
      <a class="indexterm" name="idm46734192200048"></a>

      <a class="indexterm" name="idm46734192199008"></a>

      Error number: <code class="literal">1153</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_net_packet_too_large"><code class="literal">ER_NET_PACKET_TOO_LARGE</code></a>; SQLSTATE:
      <code class="literal">08S01</code>
    </p><p>
      Message: Got a packet bigger than 'max_allowed_packet' bytes
    </p></li><li class="listitem"><p><a name="error_er_net_read_error_from_pipe"></a>
      <a class="indexterm" name="idm46734192192880"></a>

      <a class="indexterm" name="idm46734192191840"></a>

      Error number: <code class="literal">1154</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_net_read_error_from_pipe"><code class="literal">ER_NET_READ_ERROR_FROM_PIPE</code></a>;
      SQLSTATE: <code class="literal">08S01</code>
    </p><p>
      Message: Got a read error from the connection pipe
    </p></li><li class="listitem"><p><a name="error_er_net_fcntl_error"></a>
      <a class="indexterm" name="idm46734192185760"></a>

      <a class="indexterm" name="idm46734192184720"></a>

      Error number: <code class="literal">1155</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_net_fcntl_error"><code class="literal">ER_NET_FCNTL_ERROR</code></a>; SQLSTATE:
      <code class="literal">08S01</code>
    </p><p>
      Message: Got an error from fcntl()
    </p></li><li class="listitem"><p><a name="error_er_net_packets_out_of_order"></a>
      <a class="indexterm" name="idm46734192178688"></a>

      <a class="indexterm" name="idm46734192177648"></a>

      Error number: <code class="literal">1156</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_net_packets_out_of_order"><code class="literal">ER_NET_PACKETS_OUT_OF_ORDER</code></a>;
      SQLSTATE: <code class="literal">08S01</code>
    </p><p>
      Message: Got packets out of order
    </p></li><li class="listitem"><p><a name="error_er_net_uncompress_error"></a>
      <a class="indexterm" name="idm46734192171520"></a>

      <a class="indexterm" name="idm46734192170480"></a>

      Error number: <code class="literal">1157</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_net_uncompress_error"><code class="literal">ER_NET_UNCOMPRESS_ERROR</code></a>; SQLSTATE:
      <code class="literal">08S01</code>
    </p><p>
      Message: Couldn't uncompress communication packet
    </p></li><li class="listitem"><p><a name="error_er_net_read_error"></a>
      <a class="indexterm" name="idm46734192164480"></a>

      <a class="indexterm" name="idm46734192163424"></a>

      Error number: <code class="literal">1158</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_net_read_error"><code class="literal">ER_NET_READ_ERROR</code></a>; SQLSTATE:
      <code class="literal">08S01</code>
    </p><p>
      Message: Got an error reading communication packets
    </p></li><li class="listitem"><p><a name="error_er_net_read_interrupted"></a>
      <a class="indexterm" name="idm46734192157344"></a>

      <a class="indexterm" name="idm46734192156304"></a>

      Error number: <code class="literal">1159</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_net_read_interrupted"><code class="literal">ER_NET_READ_INTERRUPTED</code></a>; SQLSTATE:
      <code class="literal">08S01</code>
    </p><p>
      Message: Got timeout reading communication packets
    </p></li><li class="listitem"><p><a name="error_er_net_error_on_write"></a>
      <a class="indexterm" name="idm46734192150192"></a>

      <a class="indexterm" name="idm46734192149152"></a>

      Error number: <code class="literal">1160</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_net_error_on_write"><code class="literal">ER_NET_ERROR_ON_WRITE</code></a>; SQLSTATE:
      <code class="literal">08S01</code>
    </p><p>
      Message: Got an error writing communication packets
    </p></li><li class="listitem"><p><a name="error_er_net_write_interrupted"></a>
      <a class="indexterm" name="idm46734192143104"></a>

      <a class="indexterm" name="idm46734192142064"></a>

      Error number: <code class="literal">1161</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_net_write_interrupted"><code class="literal">ER_NET_WRITE_INTERRUPTED</code></a>;
      SQLSTATE: <code class="literal">08S01</code>
    </p><p>
      Message: Got timeout writing communication packets
    </p></li><li class="listitem"><p><a name="error_er_too_long_string"></a>
      <a class="indexterm" name="idm46734192135984"></a>

      <a class="indexterm" name="idm46734192134944"></a>

      Error number: <code class="literal">1162</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_long_string"><code class="literal">ER_TOO_LONG_STRING</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Result string is longer than 'max_allowed_packet' bytes
    </p></li><li class="listitem"><p><a name="error_er_table_cant_handle_blob"></a>
      <a class="indexterm" name="idm46734192128816"></a>

      <a class="indexterm" name="idm46734192127776"></a>

      Error number: <code class="literal">1163</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_cant_handle_blob"><code class="literal">ER_TABLE_CANT_HANDLE_BLOB</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: The used table type doesn't support BLOB/TEXT columns
    </p></li><li class="listitem"><p><a name="error_er_table_cant_handle_auto_increment"></a>
      <a class="indexterm" name="idm46734192121568"></a>

      <a class="indexterm" name="idm46734192120528"></a>

      Error number: <code class="literal">1164</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_cant_handle_auto_increment"><code class="literal">ER_TABLE_CANT_HANDLE_AUTO_INCREMENT</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: The used table type doesn't support AUTO_INCREMENT
      columns
    </p></li><li class="listitem"><p><a name="error_er_unused3"></a>
      <a class="indexterm" name="idm46734192114448"></a>

      <a class="indexterm" name="idm46734192113408"></a>

      Error number: <code class="literal">1165</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unused3"><code class="literal">ER_UNUSED3</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: INSERT DELAYED can't be used with table '%s' because it
      is locked with LOCK TABLES
    </p></li><li class="listitem"><p><a name="error_er_wrong_column_name"></a>
      <a class="indexterm" name="idm46734192107280"></a>

      <a class="indexterm" name="idm46734192106240"></a>

      Error number: <code class="literal">1166</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_column_name"><code class="literal">ER_WRONG_COLUMN_NAME</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Incorrect column name '%s'
    </p></li><li class="listitem"><p><a name="error_er_wrong_key_column"></a>
      <a class="indexterm" name="idm46734192100208"></a>

      <a class="indexterm" name="idm46734192099168"></a>

      Error number: <code class="literal">1167</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_key_column"><code class="literal">ER_WRONG_KEY_COLUMN</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: The used storage engine can't index column '%s'
    </p></li><li class="listitem"><p><a name="error_er_wrong_mrg_table"></a>
      <a class="indexterm" name="idm46734192093056"></a>

      <a class="indexterm" name="idm46734192092016"></a>

      Error number: <code class="literal">1168</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_mrg_table"><code class="literal">ER_WRONG_MRG_TABLE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Unable to open underlying table which is differently
      defined or of non-MyISAM type or doesn't exist
    </p></li><li class="listitem"><p><a name="error_er_dup_unique"></a>
      <a class="indexterm" name="idm46734192085952"></a>

      <a class="indexterm" name="idm46734192084896"></a>

      Error number: <code class="literal">1169</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_dup_unique"><code class="literal">ER_DUP_UNIQUE</code></a>; SQLSTATE:
      <code class="literal">23000</code>
    </p><p>
      Message: Can't write, because of unique constraint, to table '%s'
    </p></li><li class="listitem"><p><a name="error_er_blob_key_without_length"></a>
      <a class="indexterm" name="idm46734192078800"></a>

      <a class="indexterm" name="idm46734192077760"></a>

      Error number: <code class="literal">1170</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_blob_key_without_length"><code class="literal">ER_BLOB_KEY_WITHOUT_LENGTH</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: BLOB/TEXT column '%s' used in key specification without a
      key length
    </p></li><li class="listitem"><p><a name="error_er_primary_cant_have_null"></a>
      <a class="indexterm" name="idm46734192071648"></a>

      <a class="indexterm" name="idm46734192070608"></a>

      Error number: <code class="literal">1171</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_primary_cant_have_null"><code class="literal">ER_PRIMARY_CANT_HAVE_NULL</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: All parts of a PRIMARY KEY must be NOT NULL; if you need
      NULL in a key, use UNIQUE instead
    </p></li><li class="listitem"><p><a name="error_er_too_many_rows"></a>
      <a class="indexterm" name="idm46734192064528"></a>

      <a class="indexterm" name="idm46734192063472"></a>

      Error number: <code class="literal">1172</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_many_rows"><code class="literal">ER_TOO_MANY_ROWS</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Result consisted of more than one row
    </p></li><li class="listitem"><p><a name="error_er_requires_primary_key"></a>
      <a class="indexterm" name="idm46734192057392"></a>

      <a class="indexterm" name="idm46734192056352"></a>

      Error number: <code class="literal">1173</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_requires_primary_key"><code class="literal">ER_REQUIRES_PRIMARY_KEY</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: This table type requires a primary key
    </p></li><li class="listitem"><p><a name="error_er_no_raid_compiled"></a>
      <a class="indexterm" name="idm46734192050304"></a>

      <a class="indexterm" name="idm46734192049264"></a>

      Error number: <code class="literal">1174</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_raid_compiled"><code class="literal">ER_NO_RAID_COMPILED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: This version of MySQL is not compiled with RAID support
    </p></li><li class="listitem"><p><a name="error_er_update_without_key_in_safe_mode"></a>
      <a class="indexterm" name="idm46734192043152"></a>

      <a class="indexterm" name="idm46734192042112"></a>

      Error number: <code class="literal">1175</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_update_without_key_in_safe_mode"><code class="literal">ER_UPDATE_WITHOUT_KEY_IN_SAFE_MODE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: You are using safe update mode and you tried to update a
      table without a WHERE that uses a KEY column. %s
    </p></li><li class="listitem"><p><a name="error_er_key_does_not_exits"></a>
      <a class="indexterm" name="idm46734192035872"></a>

      <a class="indexterm" name="idm46734192034832"></a>

      Error number: <code class="literal">1176</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_key_does_not_exits"><code class="literal">ER_KEY_DOES_NOT_EXITS</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Key '%s' doesn't exist in table '%s'
    </p></li><li class="listitem"><p><a name="error_er_check_no_such_table"></a>
      <a class="indexterm" name="idm46734192028784"></a>

      <a class="indexterm" name="idm46734192027744"></a>

      Error number: <code class="literal">1177</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_check_no_such_table"><code class="literal">ER_CHECK_NO_SUCH_TABLE</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Can't open table
    </p></li><li class="listitem"><p><a name="error_er_check_not_implemented"></a>
      <a class="indexterm" name="idm46734192021728"></a>

      <a class="indexterm" name="idm46734192020688"></a>

      Error number: <code class="literal">1178</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_check_not_implemented"><code class="literal">ER_CHECK_NOT_IMPLEMENTED</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: The storage engine for the table doesn't support %s
    </p></li><li class="listitem"><p><a name="error_er_cant_do_this_during_an_transaction"></a>
      <a class="indexterm" name="idm46734192014480"></a>

      <a class="indexterm" name="idm46734192013440"></a>

      Error number: <code class="literal">1179</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_do_this_during_an_transaction"><code class="literal">ER_CANT_DO_THIS_DURING_AN_TRANSACTION</code></a>;
      SQLSTATE: <code class="literal">25000</code>
    </p><p>
      Message: You are not allowed to execute this command in a
      transaction
    </p></li><li class="listitem"><p><a name="error_er_error_during_commit"></a>
      <a class="indexterm" name="idm46734192007312"></a>

      <a class="indexterm" name="idm46734192006272"></a>

      Error number: <code class="literal">1180</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_error_during_commit"><code class="literal">ER_ERROR_DURING_COMMIT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Got error %d during COMMIT
    </p></li><li class="listitem"><p><a name="error_er_error_during_rollback"></a>
      <a class="indexterm" name="idm46734192000240"></a>

      <a class="indexterm" name="idm46734191999200"></a>

      Error number: <code class="literal">1181</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_error_during_rollback"><code class="literal">ER_ERROR_DURING_ROLLBACK</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Got error %d during ROLLBACK
    </p></li><li class="listitem"><p><a name="error_er_error_during_flush_logs"></a>
      <a class="indexterm" name="idm46734191993136"></a>

      <a class="indexterm" name="idm46734191992096"></a>

      Error number: <code class="literal">1182</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_error_during_flush_logs"><code class="literal">ER_ERROR_DURING_FLUSH_LOGS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Got error %d during FLUSH_LOGS
    </p></li><li class="listitem"><p><a name="error_er_error_during_checkpoint"></a>
      <a class="indexterm" name="idm46734191986032"></a>

      <a class="indexterm" name="idm46734191984992"></a>

      Error number: <code class="literal">1183</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_error_during_checkpoint"><code class="literal">ER_ERROR_DURING_CHECKPOINT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Got error %d during CHECKPOINT
    </p></li><li class="listitem"><p><a name="error_er_new_aborting_connection"></a>
      <a class="indexterm" name="idm46734191978928"></a>

      <a class="indexterm" name="idm46734191977888"></a>

      Error number: <code class="literal">1184</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_new_aborting_connection"><code class="literal">ER_NEW_ABORTING_CONNECTION</code></a>;
      SQLSTATE: <code class="literal">08S01</code>
    </p><p>
      Message: Aborted connection %u to db: '%s' user: '%s' host: '%s'
      (%s)
    </p></li><li class="listitem"><p><a name="error_er_dump_not_implemented"></a>
      <a class="indexterm" name="idm46734191971840"></a>

      <a class="indexterm" name="idm46734191970800"></a>

      Error number: <code class="literal">1185</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_dump_not_implemented"><code class="literal">ER_DUMP_NOT_IMPLEMENTED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The storage engine for the table does not support binary
      table dump
    </p></li><li class="listitem"><p><a name="error_er_flush_master_binlog_closed"></a>
      <a class="indexterm" name="idm46734191964720"></a>

      <a class="indexterm" name="idm46734191963616"></a>

      Error number: <code class="literal">1186</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_flush_master_binlog_closed"><code class="literal">ER_FLUSH_MASTER_BINLOG_CLOSED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Binlog closed, cannot RESET MASTER
    </p></li><li class="listitem"><p><a name="error_er_index_rebuild"></a>
      <a class="indexterm" name="idm46734191957584"></a>

      <a class="indexterm" name="idm46734191956528"></a>

      Error number: <code class="literal">1187</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_index_rebuild"><code class="literal">ER_INDEX_REBUILD</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Failed rebuilding the index of dumped table '%s'
    </p></li><li class="listitem"><p><a name="error_er_master"></a>
      <a class="indexterm" name="idm46734191950496"></a>

      <a class="indexterm" name="idm46734191949456"></a>

      Error number: <code class="literal">1188</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_master"><code class="literal">ER_MASTER</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Error from master: '%s'
    </p></li><li class="listitem"><p><a name="error_er_master_net_read"></a>
      <a class="indexterm" name="idm46734191943456"></a>

      <a class="indexterm" name="idm46734191942416"></a>

      Error number: <code class="literal">1189</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_master_net_read"><code class="literal">ER_MASTER_NET_READ</code></a>; SQLSTATE:
      <code class="literal">08S01</code>
    </p><p>
      Message: Net error reading from master
    </p></li><li class="listitem"><p><a name="error_er_master_net_write"></a>
      <a class="indexterm" name="idm46734191936384"></a>

      <a class="indexterm" name="idm46734191935344"></a>

      Error number: <code class="literal">1190</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_master_net_write"><code class="literal">ER_MASTER_NET_WRITE</code></a>; SQLSTATE:
      <code class="literal">08S01</code>
    </p><p>
      Message: Net error writing to master
    </p></li><li class="listitem"><p><a name="error_er_ft_matching_key_not_found"></a>
      <a class="indexterm" name="idm46734191929312"></a>

      <a class="indexterm" name="idm46734191928272"></a>

      Error number: <code class="literal">1191</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_ft_matching_key_not_found"><code class="literal">ER_FT_MATCHING_KEY_NOT_FOUND</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Can't find FULLTEXT index matching the column list
    </p></li><li class="listitem"><p><a name="error_er_lock_or_active_transaction"></a>
      <a class="indexterm" name="idm46734191922192"></a>

      <a class="indexterm" name="idm46734191921088"></a>

      Error number: <code class="literal">1192</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_lock_or_active_transaction"><code class="literal">ER_LOCK_OR_ACTIVE_TRANSACTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Can't execute the given command because you have active
      locked tables or an active transaction
    </p></li><li class="listitem"><p><a name="error_er_unknown_system_variable"></a>
      <a class="indexterm" name="idm46734191914992"></a>

      <a class="indexterm" name="idm46734191913952"></a>

      Error number: <code class="literal">1193</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unknown_system_variable"><code class="literal">ER_UNKNOWN_SYSTEM_VARIABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Unknown system variable '%s'
    </p></li><li class="listitem"><p><a name="error_er_crashed_on_usage"></a>
      <a class="indexterm" name="idm46734191907824"></a>

      <a class="indexterm" name="idm46734191906784"></a>

      Error number: <code class="literal">1194</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_crashed_on_usage"><code class="literal">ER_CRASHED_ON_USAGE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Table '%s' is marked as crashed and should be repaired
    </p></li><li class="listitem"><p><a name="error_er_crashed_on_repair"></a>
      <a class="indexterm" name="idm46734191900704"></a>

      <a class="indexterm" name="idm46734191899664"></a>

      Error number: <code class="literal">1195</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_crashed_on_repair"><code class="literal">ER_CRASHED_ON_REPAIR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Table '%s' is marked as crashed and last (automatic?)
      repair failed
    </p></li><li class="listitem"><p><a name="error_er_warning_not_complete_rollback"></a>
      <a class="indexterm" name="idm46734191893568"></a>

      <a class="indexterm" name="idm46734191892464"></a>

      Error number: <code class="literal">1196</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warning_not_complete_rollback"><code class="literal">ER_WARNING_NOT_COMPLETE_ROLLBACK</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Some non-transactional changed tables couldn't be rolled
      back
    </p></li><li class="listitem"><p><a name="error_er_trans_cache_full"></a>
      <a class="indexterm" name="idm46734191886464"></a>

      <a class="indexterm" name="idm46734191885424"></a>

      Error number: <code class="literal">1197</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_trans_cache_full"><code class="literal">ER_TRANS_CACHE_FULL</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Multi-statement transaction required more than
      'max_binlog_cache_size' bytes of storage; increase this mysqld
      variable and try again
    </p></li><li class="listitem"><p><a name="error_er_slave_must_stop"></a>
      <a class="indexterm" name="idm46734191879280"></a>

      <a class="indexterm" name="idm46734191878240"></a>

      Error number: <code class="literal">1198</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_must_stop"><code class="literal">ER_SLAVE_MUST_STOP</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: This operation cannot be performed with a running slave;
      run STOP SLAVE first
    </p></li><li class="listitem"><p><a name="error_er_slave_not_running"></a>
      <a class="indexterm" name="idm46734191872144"></a>

      <a class="indexterm" name="idm46734191871104"></a>

      Error number: <code class="literal">1199</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_not_running"><code class="literal">ER_SLAVE_NOT_RUNNING</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: This operation requires a running slave; configure slave
      and do START SLAVE
    </p></li><li class="listitem"><p><a name="error_er_bad_slave"></a>
      <a class="indexterm" name="idm46734191865072"></a>

      <a class="indexterm" name="idm46734191864032"></a>

      Error number: <code class="literal">1200</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_bad_slave"><code class="literal">ER_BAD_SLAVE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The server is not configured as slave; fix in config file
      or with CHANGE MASTER TO
    </p></li><li class="listitem"><p><a name="error_er_master_info"></a>
      <a class="indexterm" name="idm46734191858000"></a>

      <a class="indexterm" name="idm46734191856944"></a>

      Error number: <code class="literal">1201</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_master_info"><code class="literal">ER_MASTER_INFO</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Could not initialize master info structure; more error
      messages can be found in the MySQL error log
    </p></li><li class="listitem"><p><a name="error_er_slave_thread"></a>
      <a class="indexterm" name="idm46734191850976"></a>

      <a class="indexterm" name="idm46734191849920"></a>

      Error number: <code class="literal">1202</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_thread"><code class="literal">ER_SLAVE_THREAD</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Could not create slave thread; check system resources
    </p></li><li class="listitem"><p><a name="error_er_too_many_user_connections"></a>
      <a class="indexterm" name="idm46734191843936"></a>

      <a class="indexterm" name="idm46734191842896"></a>

      Error number: <code class="literal">1203</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_many_user_connections"><code class="literal">ER_TOO_MANY_USER_CONNECTIONS</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: User %s already has more than 'max_user_connections'
      active connections
    </p></li><li class="listitem"><p><a name="error_er_set_constants_only"></a>
      <a class="indexterm" name="idm46734191836912"></a>

      <a class="indexterm" name="idm46734191835872"></a>

      Error number: <code class="literal">1204</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_set_constants_only"><code class="literal">ER_SET_CONSTANTS_ONLY</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: You may only use constant expressions with SET
    </p></li><li class="listitem"><p><a name="error_er_lock_wait_timeout"></a>
      <a class="indexterm" name="idm46734191829872"></a>

      <a class="indexterm" name="idm46734191828832"></a>

      Error number: <code class="literal">1205</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_lock_wait_timeout"><code class="literal">ER_LOCK_WAIT_TIMEOUT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Lock wait timeout exceeded; try restarting transaction
    </p><p>
      <code class="literal">InnoDB</code> reports this error when lock wait
      timeout expires. The statement that waited too long was
      <a class="link" href="glossary.html#glos_rollback" title="rollback">rolled back</a> (not the entire
      <a class="link" href="glossary.html#glos_transaction" title="transaction">transaction</a>). You can
      increase the value of the
      <a class="link" href="innodb-storage-engine.html#sysvar_innodb_lock_wait_timeout"><code class="literal">innodb_lock_wait_timeout</code></a>
      configuration option if SQL statements should wait longer for
      other transactions to complete, or decrease it if too many
      long-running transactions are causing
      <a class="link" href="glossary.html#glos_locking" title="locking">locking</a> problems and reducing
      <a class="link" href="glossary.html#glos_concurrency" title="concurrency">concurrency</a> on a busy
      system.
    </p></li><li class="listitem"><p><a name="error_er_lock_table_full"></a>
      <a class="indexterm" name="idm46734191816624"></a>

      <a class="indexterm" name="idm46734191815584"></a>

      Error number: <code class="literal">1206</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_lock_table_full"><code class="literal">ER_LOCK_TABLE_FULL</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The total number of locks exceeds the lock table size
    </p><p>
      <code class="literal">InnoDB</code> reports this error when the total number
      of locks exceeds the amount of memory devoted to managing locks.
      To avoid this error, increase the value of
      <a class="link" href="innodb-storage-engine.html#sysvar_innodb_buffer_pool_size"><code class="literal">innodb_buffer_pool_size</code></a>. Within
      an individual application, a workaround may be to break a large
      operation into smaller pieces. For example, if the error occurs
      for a large <a class="link" href="sql-statements.html#insert" title="13.2.5 INSERT Statement"><code class="literal">INSERT</code></a>, perform several
      smaller <a class="link" href="sql-statements.html#insert" title="13.2.5 INSERT Statement"><code class="literal">INSERT</code></a> operations.
    </p></li><li class="listitem"><p><a name="error_er_read_only_transaction"></a>
      <a class="indexterm" name="idm46734191804368"></a>

      <a class="indexterm" name="idm46734191803328"></a>

      Error number: <code class="literal">1207</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_read_only_transaction"><code class="literal">ER_READ_ONLY_TRANSACTION</code></a>;
      SQLSTATE: <code class="literal">25000</code>
    </p><p>
      Message: Update locks cannot be acquired during a READ UNCOMMITTED
      transaction
    </p></li><li class="listitem"><p><a name="error_er_drop_db_with_read_lock"></a>
      <a class="indexterm" name="idm46734191797216"></a>

      <a class="indexterm" name="idm46734191796176"></a>

      Error number: <code class="literal">1208</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_drop_db_with_read_lock"><code class="literal">ER_DROP_DB_WITH_READ_LOCK</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: DROP DATABASE not allowed while thread is holding global
      read lock
    </p></li><li class="listitem"><p><a name="error_er_create_db_with_read_lock"></a>
      <a class="indexterm" name="idm46734191790064"></a>

      <a class="indexterm" name="idm46734191789024"></a>

      Error number: <code class="literal">1209</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_create_db_with_read_lock"><code class="literal">ER_CREATE_DB_WITH_READ_LOCK</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: CREATE DATABASE not allowed while thread is holding
      global read lock
    </p></li><li class="listitem"><p><a name="error_er_wrong_arguments"></a>
      <a class="indexterm" name="idm46734191782960"></a>

      <a class="indexterm" name="idm46734191781920"></a>

      Error number: <code class="literal">1210</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_arguments"><code class="literal">ER_WRONG_ARGUMENTS</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Incorrect arguments to %s
    </p></li><li class="listitem"><p><a name="error_er_no_permission_to_create_user"></a>
      <a class="indexterm" name="idm46734191776016"></a>

      <a class="indexterm" name="idm46734191774912"></a>

      Error number: <code class="literal">1211</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_permission_to_create_user"><code class="literal">ER_NO_PERMISSION_TO_CREATE_USER</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: '%s'@'%s' is not allowed to create new users
    </p></li><li class="listitem"><p><a name="error_er_union_tables_in_different_dir"></a>
      <a class="indexterm" name="idm46734191768880"></a>

      <a class="indexterm" name="idm46734191767776"></a>

      Error number: <code class="literal">1212</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_union_tables_in_different_dir"><code class="literal">ER_UNION_TABLES_IN_DIFFERENT_DIR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Incorrect table definition; all MERGE tables must be in
      the same database
    </p></li><li class="listitem"><p><a name="error_er_lock_deadlock"></a>
      <a class="indexterm" name="idm46734191761808"></a>

      <a class="indexterm" name="idm46734191760752"></a>

      Error number: <code class="literal">1213</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_lock_deadlock"><code class="literal">ER_LOCK_DEADLOCK</code></a>; SQLSTATE:
      <code class="literal">40001</code>
    </p><p>
      Message: Deadlock found when trying to get lock; try restarting
      transaction
    </p><p>
      <code class="literal">InnoDB</code> reports this error when a
      <a class="link" href="glossary.html#glos_transaction" title="transaction">transaction</a> encounters a
      <a class="link" href="glossary.html#glos_deadlock" title="deadlock">deadlock</a> and is automatically
      <a class="link" href="glossary.html#glos_rollback" title="rollback">rolled back</a> so that your
      application can take corrective action. To recover from this
      error, run all the operations in this transaction again. A
      deadlock occurs when requests for locks arrive in inconsistent
      order between transactions. The transaction that was rolled back
      released all its locks, and the other transaction can now get all
      the locks it requested. Thus, when you re-run the transaction that
      was rolled back, it might have to wait for other transactions to
      complete, but typically the deadlock does not recur. If you
      encounter frequent deadlocks, make the sequence of locking
      operations (<code class="literal">LOCK TABLES</code>, <code class="literal">SELECT ...
      FOR UPDATE</code>, and so on) consistent between the different
      transactions or applications that experience the issue. See
      <a class="xref" href="innodb-storage-engine.html#innodb-deadlocks" title="14.7.5 Deadlocks in InnoDB">Section 14.7.5, “Deadlocks in InnoDB”</a> for details.
    </p></li><li class="listitem"><p><a name="error_er_table_cant_handle_ft"></a>
      <a class="indexterm" name="idm46734191748368"></a>

      <a class="indexterm" name="idm46734191747328"></a>

      Error number: <code class="literal">1214</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_cant_handle_ft"><code class="literal">ER_TABLE_CANT_HANDLE_FT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The used table type doesn't support FULLTEXT indexes
    </p></li><li class="listitem"><p><a name="error_er_cannot_add_foreign"></a>
      <a class="indexterm" name="idm46734191741200"></a>

      <a class="indexterm" name="idm46734191740160"></a>

      Error number: <code class="literal">1215</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cannot_add_foreign"><code class="literal">ER_CANNOT_ADD_FOREIGN</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Cannot add foreign key constraint
    </p></li><li class="listitem"><p><a name="error_er_no_referenced_row"></a>
      <a class="indexterm" name="idm46734191734064"></a>

      <a class="indexterm" name="idm46734191733024"></a>

      Error number: <code class="literal">1216</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_referenced_row"><code class="literal">ER_NO_REFERENCED_ROW</code></a>; SQLSTATE:
      <code class="literal">23000</code>
    </p><p>
      Message: Cannot add or update a child row: a foreign key
      constraint fails
    </p><p>
      <code class="literal">InnoDB</code> reports this error when you try to add a
      row but there is no parent row, and a
      <a class="link" href="glossary.html#glos_foreign_key_constraint" title="FOREIGN KEY constraint">foreign key
      constraint</a> fails. Add the parent row first.
    </p></li><li class="listitem"><p><a name="error_er_row_is_referenced"></a>
      <a class="indexterm" name="idm46734191724800"></a>

      <a class="indexterm" name="idm46734191723760"></a>

      Error number: <code class="literal">1217</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_row_is_referenced"><code class="literal">ER_ROW_IS_REFERENCED</code></a>; SQLSTATE:
      <code class="literal">23000</code>
    </p><p>
      Message: Cannot delete or update a parent row: a foreign key
      constraint fails
    </p><p>
      <code class="literal">InnoDB</code> reports this error when you try to
      delete a parent row that has children, and a
      <a class="link" href="glossary.html#glos_foreign_key_constraint" title="FOREIGN KEY constraint">foreign key
      constraint</a> fails. Delete the children first.
    </p></li><li class="listitem"><p><a name="error_er_connect_to_master"></a>
      <a class="indexterm" name="idm46734191715600"></a>

      <a class="indexterm" name="idm46734191714560"></a>

      Error number: <code class="literal">1218</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_connect_to_master"><code class="literal">ER_CONNECT_TO_MASTER</code></a>; SQLSTATE:
      <code class="literal">08S01</code>
    </p><p>
      Message: Error connecting to master: %s
    </p></li><li class="listitem"><p><a name="error_er_query_on_master"></a>
      <a class="indexterm" name="idm46734191708592"></a>

      <a class="indexterm" name="idm46734191707552"></a>

      Error number: <code class="literal">1219</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_query_on_master"><code class="literal">ER_QUERY_ON_MASTER</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Error running query on master: %s
    </p></li><li class="listitem"><p><a name="error_er_error_when_executing_command"></a>
      <a class="indexterm" name="idm46734191701520"></a>

      <a class="indexterm" name="idm46734191700416"></a>

      Error number: <code class="literal">1220</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_error_when_executing_command"><code class="literal">ER_ERROR_WHEN_EXECUTING_COMMAND</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Error when executing command %s: %s
    </p></li><li class="listitem"><p><a name="error_er_wrong_usage"></a>
      <a class="indexterm" name="idm46734191694480"></a>

      <a class="indexterm" name="idm46734191693424"></a>

      Error number: <code class="literal">1221</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_usage"><code class="literal">ER_WRONG_USAGE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Incorrect usage of %s and %s
    </p></li><li class="listitem"><p><a name="error_er_wrong_number_of_columns_in_select"></a>
      <a class="indexterm" name="idm46734191687504"></a>

      <a class="indexterm" name="idm46734191686464"></a>

      Error number: <code class="literal">1222</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_number_of_columns_in_select"><code class="literal">ER_WRONG_NUMBER_OF_COLUMNS_IN_SELECT</code></a>;
      SQLSTATE: <code class="literal">21000</code>
    </p><p>
      Message: The used SELECT statements have a different number of
      columns
    </p></li><li class="listitem"><p><a name="error_er_cant_update_with_readlock"></a>
      <a class="indexterm" name="idm46734191680256"></a>

      <a class="indexterm" name="idm46734191679216"></a>

      Error number: <code class="literal">1223</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_update_with_readlock"><code class="literal">ER_CANT_UPDATE_WITH_READLOCK</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Can't execute the query because you have a conflicting
      read lock
    </p></li><li class="listitem"><p><a name="error_er_mixing_not_allowed"></a>
      <a class="indexterm" name="idm46734191673040"></a>

      <a class="indexterm" name="idm46734191672000"></a>

      Error number: <code class="literal">1224</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_mixing_not_allowed"><code class="literal">ER_MIXING_NOT_ALLOWED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Mixing of transactional and non-transactional tables is
      disabled
    </p></li><li class="listitem"><p><a name="error_er_dup_argument"></a>
      <a class="indexterm" name="idm46734191665968"></a>

      <a class="indexterm" name="idm46734191664912"></a>

      Error number: <code class="literal">1225</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_dup_argument"><code class="literal">ER_DUP_ARGUMENT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Option '%s' used twice in statement
    </p></li><li class="listitem"><p><a name="error_er_user_limit_reached"></a>
      <a class="indexterm" name="idm46734191658944"></a>

      <a class="indexterm" name="idm46734191657904"></a>

      Error number: <code class="literal">1226</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_user_limit_reached"><code class="literal">ER_USER_LIMIT_REACHED</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: User '%s' has exceeded the '%s' resource (current value:
      %ld)
    </p></li><li class="listitem"><p><a name="error_er_specific_access_denied_error"></a>
      <a class="indexterm" name="idm46734191651952"></a>

      <a class="indexterm" name="idm46734191650848"></a>

      Error number: <code class="literal">1227</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_specific_access_denied_error"><code class="literal">ER_SPECIFIC_ACCESS_DENIED_ERROR</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Access denied; you need (at least one of) the %s
      privilege(s) for this operation
    </p></li><li class="listitem"><p><a name="error_er_local_variable"></a>
      <a class="indexterm" name="idm46734191644816"></a>

      <a class="indexterm" name="idm46734191643760"></a>

      Error number: <code class="literal">1228</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_local_variable"><code class="literal">ER_LOCAL_VARIABLE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Variable '%s' is a SESSION variable and can't be used
      with SET GLOBAL
    </p></li><li class="listitem"><p><a name="error_er_global_variable"></a>
      <a class="indexterm" name="idm46734191637648"></a>

      <a class="indexterm" name="idm46734191636608"></a>

      Error number: <code class="literal">1229</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_global_variable"><code class="literal">ER_GLOBAL_VARIABLE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Variable '%s' is a GLOBAL variable and should be set with
      SET GLOBAL
    </p></li><li class="listitem"><p><a name="error_er_no_default"></a>
      <a class="indexterm" name="idm46734191630640"></a>

      <a class="indexterm" name="idm46734191629584"></a>

      Error number: <code class="literal">1230</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_default"><code class="literal">ER_NO_DEFAULT</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Variable '%s' doesn't have a default value
    </p></li><li class="listitem"><p><a name="error_er_wrong_value_for_var"></a>
      <a class="indexterm" name="idm46734191623504"></a>

      <a class="indexterm" name="idm46734191622464"></a>

      Error number: <code class="literal">1231</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_value_for_var"><code class="literal">ER_WRONG_VALUE_FOR_VAR</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Variable '%s' can't be set to the value of '%s'
    </p></li><li class="listitem"><p><a name="error_er_wrong_type_for_var"></a>
      <a class="indexterm" name="idm46734191616416"></a>

      <a class="indexterm" name="idm46734191615376"></a>

      Error number: <code class="literal">1232</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_type_for_var"><code class="literal">ER_WRONG_TYPE_FOR_VAR</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Incorrect argument type to variable '%s'
    </p></li><li class="listitem"><p><a name="error_er_var_cant_be_read"></a>
      <a class="indexterm" name="idm46734191609264"></a>

      <a class="indexterm" name="idm46734191608224"></a>

      Error number: <code class="literal">1233</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_var_cant_be_read"><code class="literal">ER_VAR_CANT_BE_READ</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Variable '%s' can only be set, not read
    </p></li><li class="listitem"><p><a name="error_er_cant_use_option_here"></a>
      <a class="indexterm" name="idm46734191602176"></a>

      <a class="indexterm" name="idm46734191601136"></a>

      Error number: <code class="literal">1234</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_use_option_here"><code class="literal">ER_CANT_USE_OPTION_HERE</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Incorrect usage/placement of '%s'
    </p></li><li class="listitem"><p><a name="error_er_not_supported_yet"></a>
      <a class="indexterm" name="idm46734191595040"></a>

      <a class="indexterm" name="idm46734191594000"></a>

      Error number: <code class="literal">1235</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_not_supported_yet"><code class="literal">ER_NOT_SUPPORTED_YET</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: This version of MySQL doesn't yet support '%s'
    </p></li><li class="listitem"><p><a name="error_er_master_fatal_error_reading_binlog"></a>
      <a class="indexterm" name="idm46734191587904"></a>

      <a class="indexterm" name="idm46734191586864"></a>

      Error number: <code class="literal">1236</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_master_fatal_error_reading_binlog"><code class="literal">ER_MASTER_FATAL_ERROR_READING_BINLOG</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Got fatal error %d from master when reading data from
      binary log: '%s'
    </p></li><li class="listitem"><p><a name="error_er_slave_ignored_table"></a>
      <a class="indexterm" name="idm46734191580720"></a>

      <a class="indexterm" name="idm46734191579680"></a>

      Error number: <code class="literal">1237</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_ignored_table"><code class="literal">ER_SLAVE_IGNORED_TABLE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Slave SQL thread ignored the query because of
      replicate-*-table rules
    </p></li><li class="listitem"><p><a name="error_er_incorrect_global_local_var"></a>
      <a class="indexterm" name="idm46734191573600"></a>

      <a class="indexterm" name="idm46734191572496"></a>

      Error number: <code class="literal">1238</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_incorrect_global_local_var"><code class="literal">ER_INCORRECT_GLOBAL_LOCAL_VAR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Variable '%s' is a %s variable
    </p></li><li class="listitem"><p><a name="error_er_wrong_fk_def"></a>
      <a class="indexterm" name="idm46734191566528"></a>

      <a class="indexterm" name="idm46734191565472"></a>

      Error number: <code class="literal">1239</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_fk_def"><code class="literal">ER_WRONG_FK_DEF</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Incorrect foreign key definition for '%s': %s
    </p></li><li class="listitem"><p><a name="error_er_key_ref_do_not_match_table_ref"></a>
      <a class="indexterm" name="idm46734191559456"></a>

      <a class="indexterm" name="idm46734191558352"></a>

      Error number: <code class="literal">1240</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_key_ref_do_not_match_table_ref"><code class="literal">ER_KEY_REF_DO_NOT_MATCH_TABLE_REF</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Key reference and table reference don't match
    </p></li><li class="listitem"><p><a name="error_er_operand_columns"></a>
      <a class="indexterm" name="idm46734191552320"></a>

      <a class="indexterm" name="idm46734191551280"></a>

      Error number: <code class="literal">1241</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_operand_columns"><code class="literal">ER_OPERAND_COLUMNS</code></a>; SQLSTATE:
      <code class="literal">21000</code>
    </p><p>
      Message: Operand should contain %d column(s)
    </p></li><li class="listitem"><p><a name="error_er_subquery_no_1_row"></a>
      <a class="indexterm" name="idm46734191545216"></a>

      <a class="indexterm" name="idm46734191544176"></a>

      Error number: <code class="literal">1242</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_subquery_no_1_row"><code class="literal">ER_SUBQUERY_NO_1_ROW</code></a>; SQLSTATE:
      <code class="literal">21000</code>
    </p><p>
      Message: Subquery returns more than 1 row
    </p></li><li class="listitem"><p><a name="error_er_unknown_stmt_handler"></a>
      <a class="indexterm" name="idm46734191538272"></a>

      <a class="indexterm" name="idm46734191537232"></a>

      Error number: <code class="literal">1243</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unknown_stmt_handler"><code class="literal">ER_UNKNOWN_STMT_HANDLER</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Unknown prepared statement handler (%.*s) given to %s
    </p></li><li class="listitem"><p><a name="error_er_corrupt_help_db"></a>
      <a class="indexterm" name="idm46734191531104"></a>

      <a class="indexterm" name="idm46734191530064"></a>

      Error number: <code class="literal">1244</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_corrupt_help_db"><code class="literal">ER_CORRUPT_HELP_DB</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Help database is corrupt or does not exist
    </p></li><li class="listitem"><p><a name="error_er_cyclic_reference"></a>
      <a class="indexterm" name="idm46734191523952"></a>

      <a class="indexterm" name="idm46734191522912"></a>

      Error number: <code class="literal">1245</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cyclic_reference"><code class="literal">ER_CYCLIC_REFERENCE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Cyclic reference on subqueries
    </p></li><li class="listitem"><p><a name="error_er_auto_convert"></a>
      <a class="indexterm" name="idm46734191516928"></a>

      <a class="indexterm" name="idm46734191515872"></a>

      Error number: <code class="literal">1246</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_auto_convert"><code class="literal">ER_AUTO_CONVERT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Converting column '%s' from %s to %s
    </p></li><li class="listitem"><p><a name="error_er_illegal_reference"></a>
      <a class="indexterm" name="idm46734191509856"></a>

      <a class="indexterm" name="idm46734191508816"></a>

      Error number: <code class="literal">1247</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_illegal_reference"><code class="literal">ER_ILLEGAL_REFERENCE</code></a>; SQLSTATE:
      <code class="literal">42S22</code>
    </p><p>
      Message: Reference '%s' not supported (%s)
    </p></li><li class="listitem"><p><a name="error_er_derived_must_have_alias"></a>
      <a class="indexterm" name="idm46734191502784"></a>

      <a class="indexterm" name="idm46734191501744"></a>

      Error number: <code class="literal">1248</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_derived_must_have_alias"><code class="literal">ER_DERIVED_MUST_HAVE_ALIAS</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Every derived table must have its own alias
    </p></li><li class="listitem"><p><a name="error_er_select_reduced"></a>
      <a class="indexterm" name="idm46734191495776"></a>

      <a class="indexterm" name="idm46734191494720"></a>

      Error number: <code class="literal">1249</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_select_reduced"><code class="literal">ER_SELECT_REDUCED</code></a>; SQLSTATE:
      <code class="literal">01000</code>
    </p><p>
      Message: Select %u was reduced during optimization
    </p></li><li class="listitem"><p><a name="error_er_tablename_not_allowed_here"></a>
      <a class="indexterm" name="idm46734191488704"></a>

      <a class="indexterm" name="idm46734191487600"></a>

      Error number: <code class="literal">1250</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_tablename_not_allowed_here"><code class="literal">ER_TABLENAME_NOT_ALLOWED_HERE</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Table '%s' from one of the SELECTs cannot be used in %s
    </p></li><li class="listitem"><p><a name="error_er_not_supported_auth_mode"></a>
      <a class="indexterm" name="idm46734191481488"></a>

      <a class="indexterm" name="idm46734191480448"></a>

      Error number: <code class="literal">1251</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_not_supported_auth_mode"><code class="literal">ER_NOT_SUPPORTED_AUTH_MODE</code></a>;
      SQLSTATE: <code class="literal">08004</code>
    </p><p>
      Message: Client does not support authentication protocol requested
      by server; consider upgrading MySQL client
    </p></li><li class="listitem"><p><a name="error_er_spatial_cant_have_null"></a>
      <a class="indexterm" name="idm46734191474304"></a>

      <a class="indexterm" name="idm46734191473264"></a>

      Error number: <code class="literal">1252</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_spatial_cant_have_null"><code class="literal">ER_SPATIAL_CANT_HAVE_NULL</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: All parts of a SPATIAL index must be NOT NULL
    </p></li><li class="listitem"><p><a name="error_er_collation_charset_mismatch"></a>
      <a class="indexterm" name="idm46734191467184"></a>

      <a class="indexterm" name="idm46734191466080"></a>

      Error number: <code class="literal">1253</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_collation_charset_mismatch"><code class="literal">ER_COLLATION_CHARSET_MISMATCH</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: COLLATION '%s' is not valid for CHARACTER SET '%s'
    </p></li><li class="listitem"><p><a name="error_er_slave_was_running"></a>
      <a class="indexterm" name="idm46734191460048"></a>

      <a class="indexterm" name="idm46734191459008"></a>

      Error number: <code class="literal">1254</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_was_running"><code class="literal">ER_SLAVE_WAS_RUNNING</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Slave is already running
    </p></li><li class="listitem"><p><a name="error_er_slave_was_not_running"></a>
      <a class="indexterm" name="idm46734191452976"></a>

      <a class="indexterm" name="idm46734191451936"></a>

      Error number: <code class="literal">1255</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_was_not_running"><code class="literal">ER_SLAVE_WAS_NOT_RUNNING</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Slave already has been stopped
    </p></li><li class="listitem"><p><a name="error_er_too_big_for_uncompress"></a>
      <a class="indexterm" name="idm46734191445872"></a>

      <a class="indexterm" name="idm46734191444832"></a>

      Error number: <code class="literal">1256</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_big_for_uncompress"><code class="literal">ER_TOO_BIG_FOR_UNCOMPRESS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Uncompressed data size too large; the maximum size is %d
      (probably, length of uncompressed data was corrupted)
    </p></li><li class="listitem"><p><a name="error_er_zlib_z_mem_error"></a>
      <a class="indexterm" name="idm46734191438672"></a>

      <a class="indexterm" name="idm46734191437632"></a>

      Error number: <code class="literal">1257</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_zlib_z_mem_error"><code class="literal">ER_ZLIB_Z_MEM_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: ZLIB: Not enough memory
    </p></li><li class="listitem"><p><a name="error_er_zlib_z_buf_error"></a>
      <a class="indexterm" name="idm46734191431600"></a>

      <a class="indexterm" name="idm46734191430560"></a>

      Error number: <code class="literal">1258</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_zlib_z_buf_error"><code class="literal">ER_ZLIB_Z_BUF_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: ZLIB: Not enough room in the output buffer (probably,
      length of uncompressed data was corrupted)
    </p></li><li class="listitem"><p><a name="error_er_zlib_z_data_error"></a>
      <a class="indexterm" name="idm46734191424432"></a>

      <a class="indexterm" name="idm46734191423392"></a>

      Error number: <code class="literal">1259</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_zlib_z_data_error"><code class="literal">ER_ZLIB_Z_DATA_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: ZLIB: Input data corrupted
    </p></li><li class="listitem"><p><a name="error_er_cut_value_group_concat"></a>
      <a class="indexterm" name="idm46734191417344"></a>

      <a class="indexterm" name="idm46734191416304"></a>

      Error number: <code class="literal">1260</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cut_value_group_concat"><code class="literal">ER_CUT_VALUE_GROUP_CONCAT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Row %u was cut by GROUP_CONCAT()
    </p></li><li class="listitem"><p><a name="error_er_warn_too_few_records"></a>
      <a class="indexterm" name="idm46734191410416"></a>

      <a class="indexterm" name="idm46734191409376"></a>

      Error number: <code class="literal">1261</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_too_few_records"><code class="literal">ER_WARN_TOO_FEW_RECORDS</code></a>; SQLSTATE:
      <code class="literal">01000</code>
    </p><p>
      Message: Row %ld doesn't contain data for all columns
    </p></li><li class="listitem"><p><a name="error_er_warn_too_many_records"></a>
      <a class="indexterm" name="idm46734191403392"></a>

      <a class="indexterm" name="idm46734191402352"></a>

      Error number: <code class="literal">1262</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_too_many_records"><code class="literal">ER_WARN_TOO_MANY_RECORDS</code></a>;
      SQLSTATE: <code class="literal">01000</code>
    </p><p>
      Message: Row %ld was truncated; it contained more data than there
      were input columns
    </p></li><li class="listitem"><p><a name="error_er_warn_null_to_notnull"></a>
      <a class="indexterm" name="idm46734191396224"></a>

      <a class="indexterm" name="idm46734191395184"></a>

      Error number: <code class="literal">1263</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_null_to_notnull"><code class="literal">ER_WARN_NULL_TO_NOTNULL</code></a>; SQLSTATE:
      <code class="literal">22004</code>
    </p><p>
      Message: Column set to default value; NULL supplied to NOT NULL
      column '%s' at row %ld
    </p></li><li class="listitem"><p><a name="error_er_warn_data_out_of_range"></a>
      <a class="indexterm" name="idm46734191389264"></a>

      <a class="indexterm" name="idm46734191388224"></a>

      Error number: <code class="literal">1264</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_data_out_of_range"><code class="literal">ER_WARN_DATA_OUT_OF_RANGE</code></a>;
      SQLSTATE: <code class="literal">22003</code>
    </p><p>
      Message: Out of range value for column '%s' at row %ld
    </p></li><li class="listitem"><p><a name="error_warn_data_truncated"></a>
      <a class="indexterm" name="idm46734191382320"></a>

      <a class="indexterm" name="idm46734191381280"></a>

      Error number: <code class="literal">1265</code>; Symbol:
      <a class="link" href="error-handling.html#error_warn_data_truncated"><code class="literal">WARN_DATA_TRUNCATED</code></a>; SQLSTATE:
      <code class="literal">01000</code>
    </p><p>
      Message: Data truncated for column '%s' at row %ld
    </p></li><li class="listitem"><p><a name="error_er_warn_using_other_handler"></a>
      <a class="indexterm" name="idm46734191375360"></a>

      <a class="indexterm" name="idm46734191374320"></a>

      Error number: <code class="literal">1266</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_using_other_handler"><code class="literal">ER_WARN_USING_OTHER_HANDLER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Using storage engine %s for table '%s'
    </p></li><li class="listitem"><p><a name="error_er_cant_aggregate_2collations"></a>
      <a class="indexterm" name="idm46734191368176"></a>

      <a class="indexterm" name="idm46734191367072"></a>

      Error number: <code class="literal">1267</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_aggregate_2collations"><code class="literal">ER_CANT_AGGREGATE_2COLLATIONS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Illegal mix of collations (%s,%s) and (%s,%s) for
      operation '%s'
    </p></li><li class="listitem"><p><a name="error_er_drop_user"></a>
      <a class="indexterm" name="idm46734191360992"></a>

      <a class="indexterm" name="idm46734191359952"></a>

      Error number: <code class="literal">1268</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_drop_user"><code class="literal">ER_DROP_USER</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Cannot drop one or more of the requested users
    </p></li><li class="listitem"><p><a name="error_er_revoke_grants"></a>
      <a class="indexterm" name="idm46734191353984"></a>

      <a class="indexterm" name="idm46734191352928"></a>

      Error number: <code class="literal">1269</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_revoke_grants"><code class="literal">ER_REVOKE_GRANTS</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't revoke all privileges for one or more of the
      requested users
    </p></li><li class="listitem"><p><a name="error_er_cant_aggregate_3collations"></a>
      <a class="indexterm" name="idm46734191346880"></a>

      <a class="indexterm" name="idm46734191345776"></a>

      Error number: <code class="literal">1270</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_aggregate_3collations"><code class="literal">ER_CANT_AGGREGATE_3COLLATIONS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Illegal mix of collations (%s,%s), (%s,%s), (%s,%s) for
      operation '%s'
    </p></li><li class="listitem"><p><a name="error_er_cant_aggregate_ncollations"></a>
      <a class="indexterm" name="idm46734191339776"></a>

      <a class="indexterm" name="idm46734191338672"></a>

      Error number: <code class="literal">1271</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_aggregate_ncollations"><code class="literal">ER_CANT_AGGREGATE_NCOLLATIONS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Illegal mix of collations for operation '%s'
    </p></li><li class="listitem"><p><a name="error_er_variable_is_not_struct"></a>
      <a class="indexterm" name="idm46734191332576"></a>

      <a class="indexterm" name="idm46734191331536"></a>

      Error number: <code class="literal">1272</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_variable_is_not_struct"><code class="literal">ER_VARIABLE_IS_NOT_STRUCT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Variable '%s' is not a variable component (can't be used
      as XXXX.variable_name)
    </p></li><li class="listitem"><p><a name="error_er_unknown_collation"></a>
      <a class="indexterm" name="idm46734191325408"></a>

      <a class="indexterm" name="idm46734191324368"></a>

      Error number: <code class="literal">1273</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unknown_collation"><code class="literal">ER_UNKNOWN_COLLATION</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Unknown collation: '%s'
    </p></li><li class="listitem"><p><a name="error_er_slave_ignored_ssl_params"></a>
      <a class="indexterm" name="idm46734191318336"></a>

      <a class="indexterm" name="idm46734191317296"></a>

      Error number: <code class="literal">1274</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_ignored_ssl_params"><code class="literal">ER_SLAVE_IGNORED_SSL_PARAMS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: SSL parameters in CHANGE MASTER are ignored because this
      MySQL slave was compiled without SSL support; they can be used
      later if MySQL slave with SSL is started
    </p></li><li class="listitem"><p><a name="error_er_server_is_in_secure_auth_mode"></a>
      <a class="indexterm" name="idm46734191311024"></a>

      <a class="indexterm" name="idm46734191309920"></a>

      Error number: <code class="literal">1275</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_server_is_in_secure_auth_mode"><code class="literal">ER_SERVER_IS_IN_SECURE_AUTH_MODE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Server is running in --secure-auth mode, but '%s'@'%s'
      has a password in the old format; please change the password to
      the new format
    </p></li><li class="listitem"><p><a name="error_er_warn_field_resolved"></a>
      <a class="indexterm" name="idm46734191303792"></a>

      <a class="indexterm" name="idm46734191302752"></a>

      Error number: <code class="literal">1276</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_field_resolved"><code class="literal">ER_WARN_FIELD_RESOLVED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Field or reference '%s%s%s%s%s' of SELECT #%d was
      resolved in SELECT #%d
    </p></li><li class="listitem"><p><a name="error_er_bad_slave_until_cond"></a>
      <a class="indexterm" name="idm46734191296672"></a>

      <a class="indexterm" name="idm46734191295632"></a>

      Error number: <code class="literal">1277</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_bad_slave_until_cond"><code class="literal">ER_BAD_SLAVE_UNTIL_COND</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Incorrect parameter or combination of parameters for
      START SLAVE UNTIL
    </p></li><li class="listitem"><p><a name="error_er_missing_skip_slave"></a>
      <a class="indexterm" name="idm46734191289552"></a>

      <a class="indexterm" name="idm46734191288512"></a>

      Error number: <code class="literal">1278</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_missing_skip_slave"><code class="literal">ER_MISSING_SKIP_SLAVE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: It is recommended to use --skip-slave-start when doing
      step-by-step replication with START SLAVE UNTIL; otherwise, you
      will get problems if you get an unexpected slave's mysqld restart
    </p></li><li class="listitem"><p><a name="error_er_until_cond_ignored"></a>
      <a class="indexterm" name="idm46734191282304"></a>

      <a class="indexterm" name="idm46734191281264"></a>

      Error number: <code class="literal">1279</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_until_cond_ignored"><code class="literal">ER_UNTIL_COND_IGNORED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: SQL thread is not to be started so UNTIL options are
      ignored
    </p></li><li class="listitem"><p><a name="error_er_wrong_name_for_index"></a>
      <a class="indexterm" name="idm46734191275200"></a>

      <a class="indexterm" name="idm46734191274160"></a>

      Error number: <code class="literal">1280</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_name_for_index"><code class="literal">ER_WRONG_NAME_FOR_INDEX</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Incorrect index name '%s'
    </p></li><li class="listitem"><p><a name="error_er_wrong_name_for_catalog"></a>
      <a class="indexterm" name="idm46734191268064"></a>

      <a class="indexterm" name="idm46734191267024"></a>

      Error number: <code class="literal">1281</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_name_for_catalog"><code class="literal">ER_WRONG_NAME_FOR_CATALOG</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Incorrect catalog name '%s'
    </p></li><li class="listitem"><p><a name="error_er_warn_qc_resize"></a>
      <a class="indexterm" name="idm46734191261008"></a>

      <a class="indexterm" name="idm46734191259952"></a>

      Error number: <code class="literal">1282</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_qc_resize"><code class="literal">ER_WARN_QC_RESIZE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Query cache failed to set size %lu; new query cache size
      is %lu
    </p></li><li class="listitem"><p><a name="error_er_bad_ft_column"></a>
      <a class="indexterm" name="idm46734191253888"></a>

      <a class="indexterm" name="idm46734191252832"></a>

      Error number: <code class="literal">1283</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_bad_ft_column"><code class="literal">ER_BAD_FT_COLUMN</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Column '%s' cannot be part of FULLTEXT index
    </p></li><li class="listitem"><p><a name="error_er_unknown_key_cache"></a>
      <a class="indexterm" name="idm46734191246816"></a>

      <a class="indexterm" name="idm46734191245776"></a>

      Error number: <code class="literal">1284</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unknown_key_cache"><code class="literal">ER_UNKNOWN_KEY_CACHE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Unknown key cache '%s'
    </p></li><li class="listitem"><p><a name="error_er_warn_hostname_wont_work"></a>
      <a class="indexterm" name="idm46734191239744"></a>

      <a class="indexterm" name="idm46734191238704"></a>

      Error number: <code class="literal">1285</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_hostname_wont_work"><code class="literal">ER_WARN_HOSTNAME_WONT_WORK</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: MySQL is started in --skip-name-resolve mode; you must
      restart it without this switch for this grant to work
    </p></li><li class="listitem"><p><a name="error_er_unknown_storage_engine"></a>
      <a class="indexterm" name="idm46734191232496"></a>

      <a class="indexterm" name="idm46734191231456"></a>

      Error number: <code class="literal">1286</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unknown_storage_engine"><code class="literal">ER_UNKNOWN_STORAGE_ENGINE</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Unknown storage engine '%s'
    </p></li><li class="listitem"><p><a name="error_er_warn_deprecated_syntax"></a>
      <a class="indexterm" name="idm46734191225440"></a>

      <a class="indexterm" name="idm46734191224400"></a>

      Error number: <code class="literal">1287</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_deprecated_syntax"><code class="literal">ER_WARN_DEPRECATED_SYNTAX</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: '%s' is deprecated and will be removed in a future
      release. Please use %s instead
    </p></li><li class="listitem"><p><a name="error_er_non_updatable_table"></a>
      <a class="indexterm" name="idm46734191218336"></a>

      <a class="indexterm" name="idm46734191217296"></a>

      Error number: <code class="literal">1288</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_non_updatable_table"><code class="literal">ER_NON_UPDATABLE_TABLE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The target table %s of the %s is not updatable
    </p></li><li class="listitem"><p><a name="error_er_feature_disabled"></a>
      <a class="indexterm" name="idm46734191211248"></a>

      <a class="indexterm" name="idm46734191210208"></a>

      Error number: <code class="literal">1289</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_feature_disabled"><code class="literal">ER_FEATURE_DISABLED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The '%s' feature is disabled; you need MySQL built with
      '%s' to have it working
    </p></li><li class="listitem"><p><a name="error_er_option_prevents_statement"></a>
      <a class="indexterm" name="idm46734191204048"></a>

      <a class="indexterm" name="idm46734191203008"></a>

      Error number: <code class="literal">1290</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_option_prevents_statement"><code class="literal">ER_OPTION_PREVENTS_STATEMENT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The MySQL server is running with the %s option so it
      cannot execute this statement
    </p></li><li class="listitem"><p><a name="error_er_duplicated_value_in_type"></a>
      <a class="indexterm" name="idm46734191196880"></a>

      <a class="indexterm" name="idm46734191195840"></a>

      Error number: <code class="literal">1291</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_duplicated_value_in_type"><code class="literal">ER_DUPLICATED_VALUE_IN_TYPE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Column '%s' has duplicated value '%s' in %s
    </p></li><li class="listitem"><p><a name="error_er_truncated_wrong_value"></a>
      <a class="indexterm" name="idm46734191189808"></a>

      <a class="indexterm" name="idm46734191188768"></a>

      Error number: <code class="literal">1292</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_truncated_wrong_value"><code class="literal">ER_TRUNCATED_WRONG_VALUE</code></a>;
      SQLSTATE: <code class="literal">22007</code>
    </p><p>
      Message: Truncated incorrect %s value: '%s'
    </p></li><li class="listitem"><p><a name="error_er_too_much_auto_timestamp_cols"></a>
      <a class="indexterm" name="idm46734191182832"></a>

      <a class="indexterm" name="idm46734191181728"></a>

      Error number: <code class="literal">1293</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_much_auto_timestamp_cols"><code class="literal">ER_TOO_MUCH_AUTO_TIMESTAMP_COLS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Incorrect table definition; there can be only one
      TIMESTAMP column with CURRENT_TIMESTAMP in DEFAULT or ON UPDATE
      clause
    </p></li><li class="listitem"><p><a name="error_er_invalid_on_update"></a>
      <a class="indexterm" name="idm46734422392544"></a>

      <a class="indexterm" name="idm46734422391504"></a>

      Error number: <code class="literal">1294</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_on_update"><code class="literal">ER_INVALID_ON_UPDATE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Invalid ON UPDATE clause for '%s' column
    </p></li><li class="listitem"><p><a name="error_er_unsupported_ps"></a>
      <a class="indexterm" name="idm46734422385632"></a>

      <a class="indexterm" name="idm46734422384576"></a>

      Error number: <code class="literal">1295</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unsupported_ps"><code class="literal">ER_UNSUPPORTED_PS</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: This command is not supported in the prepared statement
      protocol yet
    </p></li><li class="listitem"><p><a name="error_er_get_errmsg"></a>
      <a class="indexterm" name="idm46734422378704"></a>

      <a class="indexterm" name="idm46734422377648"></a>

      Error number: <code class="literal">1296</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_get_errmsg"><code class="literal">ER_GET_ERRMSG</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Got error %d '%s' from %s
    </p></li><li class="listitem"><p><a name="error_er_get_temporary_errmsg"></a>
      <a class="indexterm" name="idm46734422371840"></a>

      <a class="indexterm" name="idm46734422370800"></a>

      Error number: <code class="literal">1297</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_get_temporary_errmsg"><code class="literal">ER_GET_TEMPORARY_ERRMSG</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Got temporary error %d '%s' from %s
    </p></li><li class="listitem"><p><a name="error_er_unknown_time_zone"></a>
      <a class="indexterm" name="idm46734422364880"></a>

      <a class="indexterm" name="idm46734422363840"></a>

      Error number: <code class="literal">1298</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unknown_time_zone"><code class="literal">ER_UNKNOWN_TIME_ZONE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Unknown or incorrect time zone: '%s'
    </p></li><li class="listitem"><p><a name="error_er_warn_invalid_timestamp"></a>
      <a class="indexterm" name="idm46734422357920"></a>

      <a class="indexterm" name="idm46734422356880"></a>

      Error number: <code class="literal">1299</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_invalid_timestamp"><code class="literal">ER_WARN_INVALID_TIMESTAMP</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Invalid TIMESTAMP value in column '%s' at row %ld
    </p></li><li class="listitem"><p><a name="error_er_invalid_character_string"></a>
      <a class="indexterm" name="idm46734422350928"></a>

      <a class="indexterm" name="idm46734422349888"></a>

      Error number: <code class="literal">1300</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_character_string"><code class="literal">ER_INVALID_CHARACTER_STRING</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Invalid %s character string: '%s'
    </p></li><li class="listitem"><p><a name="error_er_warn_allowed_packet_overflowed"></a>
      <a class="indexterm" name="idm46734422344016"></a>

      <a class="indexterm" name="idm46734422342976"></a>

      Error number: <code class="literal">1301</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_allowed_packet_overflowed"><code class="literal">ER_WARN_ALLOWED_PACKET_OVERFLOWED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Result of %s() was larger than max_allowed_packet (%ld) -
      truncated
    </p></li><li class="listitem"><p><a name="error_er_conflicting_declarations"></a>
      <a class="indexterm" name="idm46734422337040"></a>

      <a class="indexterm" name="idm46734422336000"></a>

      Error number: <code class="literal">1302</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_conflicting_declarations"><code class="literal">ER_CONFLICTING_DECLARATIONS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Conflicting declarations: '%s%s' and '%s%s'
    </p></li><li class="listitem"><p><a name="error_er_sp_no_recursive_create"></a>
      <a class="indexterm" name="idm46734422330048"></a>

      <a class="indexterm" name="idm46734422329008"></a>

      Error number: <code class="literal">1303</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_no_recursive_create"><code class="literal">ER_SP_NO_RECURSIVE_CREATE</code></a>;
      SQLSTATE: <code class="literal">2F003</code>
    </p><p>
      Message: Can't create a %s from within another stored routine
    </p></li><li class="listitem"><p><a name="error_er_sp_already_exists"></a>
      <a class="indexterm" name="idm46734422323040"></a>

      <a class="indexterm" name="idm46734422322000"></a>

      Error number: <code class="literal">1304</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_already_exists"><code class="literal">ER_SP_ALREADY_EXISTS</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: %s %s already exists
    </p></li><li class="listitem"><p><a name="error_er_sp_does_not_exist"></a>
      <a class="indexterm" name="idm46734422316160"></a>

      <a class="indexterm" name="idm46734422315120"></a>

      Error number: <code class="literal">1305</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_does_not_exist"><code class="literal">ER_SP_DOES_NOT_EXIST</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: %s %s does not exist
    </p></li><li class="listitem"><p><a name="error_er_sp_drop_failed"></a>
      <a class="indexterm" name="idm46734422309328"></a>

      <a class="indexterm" name="idm46734422308272"></a>

      Error number: <code class="literal">1306</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_drop_failed"><code class="literal">ER_SP_DROP_FAILED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Failed to DROP %s %s
    </p></li><li class="listitem"><p><a name="error_er_sp_store_failed"></a>
      <a class="indexterm" name="idm46734422302464"></a>

      <a class="indexterm" name="idm46734422301424"></a>

      Error number: <code class="literal">1307</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_store_failed"><code class="literal">ER_SP_STORE_FAILED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Failed to CREATE %s %s
    </p></li><li class="listitem"><p><a name="error_er_sp_lilabel_mismatch"></a>
      <a class="indexterm" name="idm46734191177312"></a>

      <a class="indexterm" name="idm46734191176304"></a>

      Error number: <code class="literal">1308</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_lilabel_mismatch"><code class="literal">ER_SP_LILABEL_MISMATCH</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: %s with no matching label: %s
    </p></li><li class="listitem"><p><a name="error_er_sp_label_redefine"></a>
      <a class="indexterm" name="idm46734191171280"></a>

      <a class="indexterm" name="idm46734191170272"></a>

      Error number: <code class="literal">1309</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_label_redefine"><code class="literal">ER_SP_LABEL_REDEFINE</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Redefining label %s
    </p></li><li class="listitem"><p><a name="error_er_sp_label_mismatch"></a>
      <a class="indexterm" name="idm46734191165248"></a>

      <a class="indexterm" name="idm46734191164240"></a>

      Error number: <code class="literal">1310</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_label_mismatch"><code class="literal">ER_SP_LABEL_MISMATCH</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: End-label %s without match
    </p></li><li class="listitem"><p><a name="error_er_sp_uninit_var"></a>
      <a class="indexterm" name="idm46734191159216"></a>

      <a class="indexterm" name="idm46734191158208"></a>

      Error number: <code class="literal">1311</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_uninit_var"><code class="literal">ER_SP_UNINIT_VAR</code></a>; SQLSTATE:
      <code class="literal">01000</code>
    </p><p>
      Message: Referring to uninitialized variable %s
    </p></li><li class="listitem"><p><a name="error_er_sp_badselect"></a>
      <a class="indexterm" name="idm46734191153104"></a>

      <a class="indexterm" name="idm46734191152096"></a>

      Error number: <code class="literal">1312</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_badselect"><code class="literal">ER_SP_BADSELECT</code></a>; SQLSTATE:
      <code class="literal">0A000</code>
    </p><p>
      Message: PROCEDURE %s can't return a result set in the given
      context
    </p></li><li class="listitem"><p><a name="error_er_sp_badreturn"></a>
      <a class="indexterm" name="idm46734191146976"></a>

      <a class="indexterm" name="idm46734191145968"></a>

      Error number: <code class="literal">1313</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_badreturn"><code class="literal">ER_SP_BADRETURN</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: RETURN is only allowed in a FUNCTION
    </p></li><li class="listitem"><p><a name="error_er_sp_badstatement"></a>
      <a class="indexterm" name="idm46734191140864"></a>

      <a class="indexterm" name="idm46734191139856"></a>

      Error number: <code class="literal">1314</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_badstatement"><code class="literal">ER_SP_BADSTATEMENT</code></a>; SQLSTATE:
      <code class="literal">0A000</code>
    </p><p>
      Message: %s is not allowed in stored procedures
    </p></li><li class="listitem"><p><a name="error_er_update_log_deprecated_ignored"></a>
      <a class="indexterm" name="idm46734191134752"></a>

      <a class="indexterm" name="idm46734191133744"></a>

      Error number: <code class="literal">1315</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_update_log_deprecated_ignored"><code class="literal">ER_UPDATE_LOG_DEPRECATED_IGNORED</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: The update log is deprecated and replaced by the binary
      log; SET SQL_LOG_UPDATE has been ignored.
    </p></li><li class="listitem"><p><a name="error_er_update_log_deprecated_translated"></a>
      <a class="indexterm" name="idm46734191128576"></a>

      <a class="indexterm" name="idm46734191127568"></a>

      Error number: <code class="literal">1316</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_update_log_deprecated_translated"><code class="literal">ER_UPDATE_LOG_DEPRECATED_TRANSLATED</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: The update log is deprecated and replaced by the binary
      log; SET SQL_LOG_UPDATE has been translated to SET SQL_LOG_BIN.
    </p></li><li class="listitem"><p><a name="error_er_query_interrupted"></a>
      <a class="indexterm" name="idm46734191122384"></a>

      <a class="indexterm" name="idm46734191121376"></a>

      Error number: <code class="literal">1317</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_query_interrupted"><code class="literal">ER_QUERY_INTERRUPTED</code></a>; SQLSTATE:
      <code class="literal">70100</code>
    </p><p>
      Message: Query execution was interrupted
    </p></li><li class="listitem"><p><a name="error_er_sp_wrong_no_of_args"></a>
      <a class="indexterm" name="idm46734191116352"></a>

      <a class="indexterm" name="idm46734191115344"></a>

      Error number: <code class="literal">1318</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_wrong_no_of_args"><code class="literal">ER_SP_WRONG_NO_OF_ARGS</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Incorrect number of arguments for %s %s; expected %u, got
      %u
    </p></li><li class="listitem"><p><a name="error_er_sp_cond_mismatch"></a>
      <a class="indexterm" name="idm46734191110224"></a>

      <a class="indexterm" name="idm46734191109216"></a>

      Error number: <code class="literal">1319</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_cond_mismatch"><code class="literal">ER_SP_COND_MISMATCH</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Undefined CONDITION: %s
    </p></li><li class="listitem"><p><a name="error_er_sp_noreturn"></a>
      <a class="indexterm" name="idm46734191104192"></a>

      <a class="indexterm" name="idm46734191103184"></a>

      Error number: <code class="literal">1320</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_noreturn"><code class="literal">ER_SP_NORETURN</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: No RETURN found in FUNCTION %s
    </p></li><li class="listitem"><p><a name="error_er_sp_noreturnend"></a>
      <a class="indexterm" name="idm46734191098160"></a>

      <a class="indexterm" name="idm46734191097152"></a>

      Error number: <code class="literal">1321</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_noreturnend"><code class="literal">ER_SP_NORETURNEND</code></a>; SQLSTATE:
      <code class="literal">2F005</code>
    </p><p>
      Message: FUNCTION %s ended without RETURN
    </p></li><li class="listitem"><p><a name="error_er_sp_bad_cursor_query"></a>
      <a class="indexterm" name="idm46734191092128"></a>

      <a class="indexterm" name="idm46734191091120"></a>

      Error number: <code class="literal">1322</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_bad_cursor_query"><code class="literal">ER_SP_BAD_CURSOR_QUERY</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Cursor statement must be a SELECT
    </p></li><li class="listitem"><p><a name="error_er_sp_bad_cursor_select"></a>
      <a class="indexterm" name="idm46734191086096"></a>

      <a class="indexterm" name="idm46734191085088"></a>

      Error number: <code class="literal">1323</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_bad_cursor_select"><code class="literal">ER_SP_BAD_CURSOR_SELECT</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Cursor SELECT must not have INTO
    </p></li><li class="listitem"><p><a name="error_er_sp_cursor_mismatch"></a>
      <a class="indexterm" name="idm46734191080064"></a>

      <a class="indexterm" name="idm46734191079056"></a>

      Error number: <code class="literal">1324</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_cursor_mismatch"><code class="literal">ER_SP_CURSOR_MISMATCH</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Undefined CURSOR: %s
    </p></li><li class="listitem"><p><a name="error_er_sp_cursor_already_open"></a>
      <a class="indexterm" name="idm46734191074032"></a>

      <a class="indexterm" name="idm46734191073024"></a>

      Error number: <code class="literal">1325</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_cursor_already_open"><code class="literal">ER_SP_CURSOR_ALREADY_OPEN</code></a>;
      SQLSTATE: <code class="literal">24000</code>
    </p><p>
      Message: Cursor is already open
    </p></li><li class="listitem"><p><a name="error_er_sp_cursor_not_open"></a>
      <a class="indexterm" name="idm46734191068000"></a>

      <a class="indexterm" name="idm46734191066992"></a>

      Error number: <code class="literal">1326</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_cursor_not_open"><code class="literal">ER_SP_CURSOR_NOT_OPEN</code></a>; SQLSTATE:
      <code class="literal">24000</code>
    </p><p>
      Message: Cursor is not open
    </p></li><li class="listitem"><p><a name="error_er_sp_undeclared_var"></a>
      <a class="indexterm" name="idm46734191061968"></a>

      <a class="indexterm" name="idm46734191060960"></a>

      Error number: <code class="literal">1327</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_undeclared_var"><code class="literal">ER_SP_UNDECLARED_VAR</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Undeclared variable: %s
    </p></li><li class="listitem"><p><a name="error_er_sp_wrong_no_of_fetch_args"></a>
      <a class="indexterm" name="idm46734191055936"></a>

      <a class="indexterm" name="idm46734191054928"></a>

      Error number: <code class="literal">1328</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_wrong_no_of_fetch_args"><code class="literal">ER_SP_WRONG_NO_OF_FETCH_ARGS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Incorrect number of FETCH variables
    </p></li><li class="listitem"><p><a name="error_er_sp_fetch_no_data"></a>
      <a class="indexterm" name="idm46734191049824"></a>

      <a class="indexterm" name="idm46734191048816"></a>

      Error number: <code class="literal">1329</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_fetch_no_data"><code class="literal">ER_SP_FETCH_NO_DATA</code></a>; SQLSTATE:
      <code class="literal">02000</code>
    </p><p>
      Message: No data - zero rows fetched, selected, or processed
    </p></li><li class="listitem"><p><a name="error_er_sp_dup_param"></a>
      <a class="indexterm" name="idm46734191043696"></a>

      <a class="indexterm" name="idm46734191042688"></a>

      Error number: <code class="literal">1330</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_dup_param"><code class="literal">ER_SP_DUP_PARAM</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Duplicate parameter: %s
    </p></li><li class="listitem"><p><a name="error_er_sp_dup_var"></a>
      <a class="indexterm" name="idm46734191037664"></a>

      <a class="indexterm" name="idm46734191036656"></a>

      Error number: <code class="literal">1331</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_dup_var"><code class="literal">ER_SP_DUP_VAR</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Duplicate variable: %s
    </p></li><li class="listitem"><p><a name="error_er_sp_dup_cond"></a>
      <a class="indexterm" name="idm46734191031632"></a>

      <a class="indexterm" name="idm46734191030624"></a>

      Error number: <code class="literal">1332</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_dup_cond"><code class="literal">ER_SP_DUP_COND</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Duplicate condition: %s
    </p></li><li class="listitem"><p><a name="error_er_sp_dup_curs"></a>
      <a class="indexterm" name="idm46734191025600"></a>

      <a class="indexterm" name="idm46734191024592"></a>

      Error number: <code class="literal">1333</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_dup_curs"><code class="literal">ER_SP_DUP_CURS</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Duplicate cursor: %s
    </p></li><li class="listitem"><p><a name="error_er_sp_cant_alter"></a>
      <a class="indexterm" name="idm46734191019568"></a>

      <a class="indexterm" name="idm46734191018560"></a>

      Error number: <code class="literal">1334</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_cant_alter"><code class="literal">ER_SP_CANT_ALTER</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Failed to ALTER %s %s
    </p></li><li class="listitem"><p><a name="error_er_sp_subselect_nyi"></a>
      <a class="indexterm" name="idm46734191013536"></a>

      <a class="indexterm" name="idm46734191012528"></a>

      Error number: <code class="literal">1335</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_subselect_nyi"><code class="literal">ER_SP_SUBSELECT_NYI</code></a>; SQLSTATE:
      <code class="literal">0A000</code>
    </p><p>
      Message: Subquery value not supported
    </p></li><li class="listitem"><p><a name="error_er_stmt_not_allowed_in_sf_or_trg"></a>
      <a class="indexterm" name="idm46734191007504"></a>

      <a class="indexterm" name="idm46734191006496"></a>

      Error number: <code class="literal">1336</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_stmt_not_allowed_in_sf_or_trg"><code class="literal">ER_STMT_NOT_ALLOWED_IN_SF_OR_TRG</code></a>;
      SQLSTATE: <code class="literal">0A000</code>
    </p><p>
      Message: %s is not allowed in stored function or trigger
    </p></li><li class="listitem"><p><a name="error_er_sp_varcond_after_curshndlr"></a>
      <a class="indexterm" name="idm46734191001392"></a>

      <a class="indexterm" name="idm46734191000384"></a>

      Error number: <code class="literal">1337</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_varcond_after_curshndlr"><code class="literal">ER_SP_VARCOND_AFTER_CURSHNDLR</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Variable or condition declaration after cursor or handler
      declaration
    </p></li><li class="listitem"><p><a name="error_er_sp_cursor_after_handler"></a>
      <a class="indexterm" name="idm46734190995248"></a>

      <a class="indexterm" name="idm46734190994240"></a>

      Error number: <code class="literal">1338</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_cursor_after_handler"><code class="literal">ER_SP_CURSOR_AFTER_HANDLER</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Cursor declaration after handler declaration
    </p></li><li class="listitem"><p><a name="error_er_sp_case_not_found"></a>
      <a class="indexterm" name="idm46734190989136"></a>

      <a class="indexterm" name="idm46734190988128"></a>

      Error number: <code class="literal">1339</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_case_not_found"><code class="literal">ER_SP_CASE_NOT_FOUND</code></a>; SQLSTATE:
      <code class="literal">20000</code>
    </p><p>
      Message: Case not found for CASE statement
    </p></li><li class="listitem"><p><a name="error_er_fparser_too_big_file"></a>
      <a class="indexterm" name="idm46734190983104"></a>

      <a class="indexterm" name="idm46734190982096"></a>

      Error number: <code class="literal">1340</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fparser_too_big_file"><code class="literal">ER_FPARSER_TOO_BIG_FILE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Configuration file '%s' is too big
    </p></li><li class="listitem"><p><a name="error_er_fparser_bad_header"></a>
      <a class="indexterm" name="idm46734190977072"></a>

      <a class="indexterm" name="idm46734190976064"></a>

      Error number: <code class="literal">1341</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fparser_bad_header"><code class="literal">ER_FPARSER_BAD_HEADER</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Malformed file type header in file '%s'
    </p></li><li class="listitem"><p><a name="error_er_fparser_eof_in_comment"></a>
      <a class="indexterm" name="idm46734190970960"></a>

      <a class="indexterm" name="idm46734190969952"></a>

      Error number: <code class="literal">1342</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fparser_eof_in_comment"><code class="literal">ER_FPARSER_EOF_IN_COMMENT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Unexpected end of file while parsing comment '%s'
    </p></li><li class="listitem"><p><a name="error_er_fparser_error_in_parameter"></a>
      <a class="indexterm" name="idm46734190964848"></a>

      <a class="indexterm" name="idm46734190963840"></a>

      Error number: <code class="literal">1343</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fparser_error_in_parameter"><code class="literal">ER_FPARSER_ERROR_IN_PARAMETER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Error while parsing parameter '%s' (line: '%s')
    </p></li><li class="listitem"><p><a name="error_er_fparser_eof_in_unknown_parameter"></a>
      <a class="indexterm" name="idm46734190958736"></a>

      <a class="indexterm" name="idm46734190957728"></a>

      Error number: <code class="literal">1344</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fparser_eof_in_unknown_parameter"><code class="literal">ER_FPARSER_EOF_IN_UNKNOWN_PARAMETER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Unexpected end of file while skipping unknown parameter
      '%s'
    </p></li><li class="listitem"><p><a name="error_er_view_no_explain"></a>
      <a class="indexterm" name="idm46734190952608"></a>

      <a class="indexterm" name="idm46734190951600"></a>

      Error number: <code class="literal">1345</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_no_explain"><code class="literal">ER_VIEW_NO_EXPLAIN</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: EXPLAIN/SHOW can not be issued; lacking privileges for
      underlying table
    </p></li><li class="listitem"><p><a name="error_er_frm_unknown_type"></a>
      <a class="indexterm" name="idm46734190946464"></a>

      <a class="indexterm" name="idm46734190945456"></a>

      Error number: <code class="literal">1346</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_frm_unknown_type"><code class="literal">ER_FRM_UNKNOWN_TYPE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: File '%s' has unknown type '%s' in its header
    </p></li><li class="listitem"><p><a name="error_er_wrong_object"></a>
      <a class="indexterm" name="idm46734190940352"></a>

      <a class="indexterm" name="idm46734190939344"></a>

      Error number: <code class="literal">1347</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_object"><code class="literal">ER_WRONG_OBJECT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: '%s.%s' is not %s
    </p><p>
      The named object is incorrect for the type of operation attempted
      on it. It must be an object of the named type.
    </p></li><li class="listitem"><p><a name="error_er_nonupdateable_column"></a>
      <a class="indexterm" name="idm46734190933792"></a>

      <a class="indexterm" name="idm46734190932784"></a>

      Error number: <code class="literal">1348</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_nonupdateable_column"><code class="literal">ER_NONUPDATEABLE_COLUMN</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Column '%s' is not updatable
    </p></li><li class="listitem"><p><a name="error_er_view_select_derived"></a>
      <a class="indexterm" name="idm46734190927760"></a>

      <a class="indexterm" name="idm46734190926752"></a>

      Error number: <code class="literal">1349</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_select_derived"><code class="literal">ER_VIEW_SELECT_DERIVED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: View's SELECT contains a subquery in the FROM clause
    </p><p>
      <a class="link" href="error-handling.html#error_er_view_select_derived"><code class="literal">ER_VIEW_SELECT_DERIVED</code></a> was removed
      after 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_view_select_derived_unused"></a>
      <a class="indexterm" name="idm46734190920256"></a>

      <a class="indexterm" name="idm46734190919248"></a>

      Error number: <code class="literal">1349</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_select_derived_unused"><code class="literal">ER_VIEW_SELECT_DERIVED_UNUSED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: View's SELECT contains a subquery in the FROM clause
    </p><p>
      <a class="link" href="error-handling.html#error_er_view_select_derived_unused"><code class="literal">ER_VIEW_SELECT_DERIVED_UNUSED</code></a> was
      added in 5.7.7.
    </p></li><li class="listitem"><p><a name="error_er_view_select_clause"></a>
      <a class="indexterm" name="idm46734190912752"></a>

      <a class="indexterm" name="idm46734190911744"></a>

      Error number: <code class="literal">1350</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_select_clause"><code class="literal">ER_VIEW_SELECT_CLAUSE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: View's SELECT contains a '%s' clause
    </p></li><li class="listitem"><p><a name="error_er_view_select_variable"></a>
      <a class="indexterm" name="idm46734190906640"></a>

      <a class="indexterm" name="idm46734190905632"></a>

      Error number: <code class="literal">1351</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_select_variable"><code class="literal">ER_VIEW_SELECT_VARIABLE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: View's SELECT contains a variable or parameter
    </p></li><li class="listitem"><p><a name="error_er_view_select_tmptable"></a>
      <a class="indexterm" name="idm46734190900528"></a>

      <a class="indexterm" name="idm46734190899520"></a>

      Error number: <code class="literal">1352</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_select_tmptable"><code class="literal">ER_VIEW_SELECT_TMPTABLE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: View's SELECT refers to a temporary table '%s'
    </p></li><li class="listitem"><p><a name="error_er_view_wrong_list"></a>
      <a class="indexterm" name="idm46734190894416"></a>

      <a class="indexterm" name="idm46734190893408"></a>

      Error number: <code class="literal">1353</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_wrong_list"><code class="literal">ER_VIEW_WRONG_LIST</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: View's SELECT and view's field list have different column
      counts
    </p></li><li class="listitem"><p><a name="error_er_warn_view_merge"></a>
      <a class="indexterm" name="idm46734190888272"></a>

      <a class="indexterm" name="idm46734190887264"></a>

      Error number: <code class="literal">1354</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_view_merge"><code class="literal">ER_WARN_VIEW_MERGE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: View merge algorithm can't be used here for now (assumed
      undefined algorithm)
    </p></li><li class="listitem"><p><a name="error_er_warn_view_without_key"></a>
      <a class="indexterm" name="idm46734190882112"></a>

      <a class="indexterm" name="idm46734190881104"></a>

      Error number: <code class="literal">1355</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_view_without_key"><code class="literal">ER_WARN_VIEW_WITHOUT_KEY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: View being updated does not have complete key of
      underlying table in it
    </p></li><li class="listitem"><p><a name="error_er_view_invalid"></a>
      <a class="indexterm" name="idm46734190875968"></a>

      <a class="indexterm" name="idm46734190874960"></a>

      Error number: <code class="literal">1356</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_invalid"><code class="literal">ER_VIEW_INVALID</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: View '%s.%s' references invalid table(s) or column(s) or
      function(s) or definer/invoker of view lack rights to use them
    </p></li><li class="listitem"><p><a name="error_er_sp_no_drop_sp"></a>
      <a class="indexterm" name="idm46734190869776"></a>

      <a class="indexterm" name="idm46734190868768"></a>

      Error number: <code class="literal">1357</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_no_drop_sp"><code class="literal">ER_SP_NO_DROP_SP</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't drop or alter a %s from within another stored
      routine
    </p></li><li class="listitem"><p><a name="error_er_sp_goto_in_hndlr"></a>
      <a class="indexterm" name="idm46734190863648"></a>

      <a class="indexterm" name="idm46734190862640"></a>

      Error number: <code class="literal">1358</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_goto_in_hndlr"><code class="literal">ER_SP_GOTO_IN_HNDLR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: GOTO is not allowed in a stored procedure handler
    </p></li><li class="listitem"><p><a name="error_er_trg_already_exists"></a>
      <a class="indexterm" name="idm46734190857536"></a>

      <a class="indexterm" name="idm46734190856528"></a>

      Error number: <code class="literal">1359</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_trg_already_exists"><code class="literal">ER_TRG_ALREADY_EXISTS</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Trigger already exists
    </p></li><li class="listitem"><p><a name="error_er_trg_does_not_exist"></a>
      <a class="indexterm" name="idm46734190851504"></a>

      <a class="indexterm" name="idm46734190850496"></a>

      Error number: <code class="literal">1360</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_trg_does_not_exist"><code class="literal">ER_TRG_DOES_NOT_EXIST</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Trigger does not exist
    </p></li><li class="listitem"><p><a name="error_er_trg_on_view_or_temp_table"></a>
      <a class="indexterm" name="idm46734190845472"></a>

      <a class="indexterm" name="idm46734190844464"></a>

      Error number: <code class="literal">1361</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_trg_on_view_or_temp_table"><code class="literal">ER_TRG_ON_VIEW_OR_TEMP_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Trigger's '%s' is view or temporary table
    </p></li><li class="listitem"><p><a name="error_er_trg_cant_change_row"></a>
      <a class="indexterm" name="idm46734190839360"></a>

      <a class="indexterm" name="idm46734190838352"></a>

      Error number: <code class="literal">1362</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_trg_cant_change_row"><code class="literal">ER_TRG_CANT_CHANGE_ROW</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Updating of %s row is not allowed in %strigger
    </p></li><li class="listitem"><p><a name="error_er_trg_no_such_row_in_trg"></a>
      <a class="indexterm" name="idm46734190833248"></a>

      <a class="indexterm" name="idm46734190832240"></a>

      Error number: <code class="literal">1363</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_trg_no_such_row_in_trg"><code class="literal">ER_TRG_NO_SUCH_ROW_IN_TRG</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: There is no %s row in %s trigger
    </p></li><li class="listitem"><p><a name="error_er_no_default_for_field"></a>
      <a class="indexterm" name="idm46734190827216"></a>

      <a class="indexterm" name="idm46734190826208"></a>

      Error number: <code class="literal">1364</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_default_for_field"><code class="literal">ER_NO_DEFAULT_FOR_FIELD</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Field '%s' doesn't have a default value
    </p></li><li class="listitem"><p><a name="error_er_division_by_zero"></a>
      <a class="indexterm" name="idm46734190821104"></a>

      <a class="indexterm" name="idm46734190820096"></a>

      Error number: <code class="literal">1365</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_division_by_zero"><code class="literal">ER_DIVISION_BY_ZERO</code></a>; SQLSTATE:
      <code class="literal">22012</code>
    </p><p>
      Message: Division by 0
    </p></li><li class="listitem"><p><a name="error_er_truncated_wrong_value_for_field"></a>
      <a class="indexterm" name="idm46734190815072"></a>

      <a class="indexterm" name="idm46734190814064"></a>

      Error number: <code class="literal">1366</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_truncated_wrong_value_for_field"><code class="literal">ER_TRUNCATED_WRONG_VALUE_FOR_FIELD</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Incorrect %s value: '%s' for column '%s' at row %ld
    </p></li><li class="listitem"><p><a name="error_er_illegal_value_for_type"></a>
      <a class="indexterm" name="idm46734190808944"></a>

      <a class="indexterm" name="idm46734190807936"></a>

      Error number: <code class="literal">1367</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_illegal_value_for_type"><code class="literal">ER_ILLEGAL_VALUE_FOR_TYPE</code></a>;
      SQLSTATE: <code class="literal">22007</code>
    </p><p>
      Message: Illegal %s '%s' value found during parsing
    </p></li><li class="listitem"><p><a name="error_er_view_nonupd_check"></a>
      <a class="indexterm" name="idm46734190802832"></a>

      <a class="indexterm" name="idm46734190801824"></a>

      Error number: <code class="literal">1368</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_nonupd_check"><code class="literal">ER_VIEW_NONUPD_CHECK</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: CHECK OPTION on non-updatable view '%s.%s'
    </p></li><li class="listitem"><p><a name="error_er_view_check_failed"></a>
      <a class="indexterm" name="idm46734190796720"></a>

      <a class="indexterm" name="idm46734190795712"></a>

      Error number: <code class="literal">1369</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_check_failed"><code class="literal">ER_VIEW_CHECK_FAILED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: CHECK OPTION failed '%s.%s'
    </p></li><li class="listitem"><p><a name="error_er_procaccess_denied_error"></a>
      <a class="indexterm" name="idm46734190790688"></a>

      <a class="indexterm" name="idm46734190789680"></a>

      Error number: <code class="literal">1370</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_procaccess_denied_error"><code class="literal">ER_PROCACCESS_DENIED_ERROR</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: %s command denied to user '%s'@'%s' for routine '%s'
    </p></li><li class="listitem"><p><a name="error_er_relay_log_fail"></a>
      <a class="indexterm" name="idm46734190784560"></a>

      <a class="indexterm" name="idm46734190783552"></a>

      Error number: <code class="literal">1371</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_relay_log_fail"><code class="literal">ER_RELAY_LOG_FAIL</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Failed purging old relay logs: %s
    </p></li><li class="listitem"><p><a name="error_er_passwd_length"></a>
      <a class="indexterm" name="idm46734190778528"></a>

      <a class="indexterm" name="idm46734190777520"></a>

      Error number: <code class="literal">1372</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_passwd_length"><code class="literal">ER_PASSWD_LENGTH</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Password hash should be a %d-digit hexadecimal number
    </p></li><li class="listitem"><p><a name="error_er_unknown_target_binlog"></a>
      <a class="indexterm" name="idm46734190772400"></a>

      <a class="indexterm" name="idm46734190771392"></a>

      Error number: <code class="literal">1373</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unknown_target_binlog"><code class="literal">ER_UNKNOWN_TARGET_BINLOG</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Target log not found in binlog index
    </p></li><li class="listitem"><p><a name="error_er_io_err_log_index_read"></a>
      <a class="indexterm" name="idm46734190766288"></a>

      <a class="indexterm" name="idm46734190765280"></a>

      Error number: <code class="literal">1374</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_io_err_log_index_read"><code class="literal">ER_IO_ERR_LOG_INDEX_READ</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: I/O error reading log index file
    </p></li><li class="listitem"><p><a name="error_er_binlog_purge_prohibited"></a>
      <a class="indexterm" name="idm46734190760256"></a>

      <a class="indexterm" name="idm46734190759248"></a>

      Error number: <code class="literal">1375</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_purge_prohibited"><code class="literal">ER_BINLOG_PURGE_PROHIBITED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Server configuration does not permit binlog purge
    </p></li><li class="listitem"><p><a name="error_er_fseek_fail"></a>
      <a class="indexterm" name="idm46734190754144"></a>

      <a class="indexterm" name="idm46734190753136"></a>

      Error number: <code class="literal">1376</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fseek_fail"><code class="literal">ER_FSEEK_FAIL</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Failed on fseek()
    </p></li><li class="listitem"><p><a name="error_er_binlog_purge_fatal_err"></a>
      <a class="indexterm" name="idm46734190748112"></a>

      <a class="indexterm" name="idm46734190747104"></a>

      Error number: <code class="literal">1377</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_purge_fatal_err"><code class="literal">ER_BINLOG_PURGE_FATAL_ERR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Fatal error during log purge
    </p></li><li class="listitem"><p><a name="error_er_log_in_use"></a>
      <a class="indexterm" name="idm46734190742080"></a>

      <a class="indexterm" name="idm46734190741072"></a>

      Error number: <code class="literal">1378</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_log_in_use"><code class="literal">ER_LOG_IN_USE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: A purgeable log is in use, will not purge
    </p></li><li class="listitem"><p><a name="error_er_log_purge_unknown_err"></a>
      <a class="indexterm" name="idm46734190735968"></a>

      <a class="indexterm" name="idm46734190734960"></a>

      Error number: <code class="literal">1379</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_log_purge_unknown_err"><code class="literal">ER_LOG_PURGE_UNKNOWN_ERR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Unknown error during log purge
    </p></li><li class="listitem"><p><a name="error_er_relay_log_init"></a>
      <a class="indexterm" name="idm46734190729936"></a>

      <a class="indexterm" name="idm46734190728928"></a>

      Error number: <code class="literal">1380</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_relay_log_init"><code class="literal">ER_RELAY_LOG_INIT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Failed initializing relay log position: %s
    </p></li><li class="listitem"><p><a name="error_er_no_binary_logging"></a>
      <a class="indexterm" name="idm46734190723824"></a>

      <a class="indexterm" name="idm46734190722816"></a>

      Error number: <code class="literal">1381</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_binary_logging"><code class="literal">ER_NO_BINARY_LOGGING</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: You are not using binary logging
    </p></li><li class="listitem"><p><a name="error_er_reserved_syntax"></a>
      <a class="indexterm" name="idm46734190717792"></a>

      <a class="indexterm" name="idm46734190716784"></a>

      Error number: <code class="literal">1382</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_reserved_syntax"><code class="literal">ER_RESERVED_SYNTAX</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The '%s' syntax is reserved for purposes internal to the
      MySQL server
    </p></li><li class="listitem"><p><a name="error_er_wsas_failed"></a>
      <a class="indexterm" name="idm46734190711648"></a>

      <a class="indexterm" name="idm46734190710640"></a>

      Error number: <code class="literal">1383</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wsas_failed"><code class="literal">ER_WSAS_FAILED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: WSAStartup Failed
    </p></li><li class="listitem"><p><a name="error_er_diff_groups_proc"></a>
      <a class="indexterm" name="idm46734190705616"></a>

      <a class="indexterm" name="idm46734190704608"></a>

      Error number: <code class="literal">1384</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_diff_groups_proc"><code class="literal">ER_DIFF_GROUPS_PROC</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't handle procedures with different groups yet
    </p></li><li class="listitem"><p><a name="error_er_no_group_for_proc"></a>
      <a class="indexterm" name="idm46734190699504"></a>

      <a class="indexterm" name="idm46734190698496"></a>

      Error number: <code class="literal">1385</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_group_for_proc"><code class="literal">ER_NO_GROUP_FOR_PROC</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Select must have a group with this procedure
    </p></li><li class="listitem"><p><a name="error_er_order_with_proc"></a>
      <a class="indexterm" name="idm46734190693392"></a>

      <a class="indexterm" name="idm46734190692384"></a>

      Error number: <code class="literal">1386</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_order_with_proc"><code class="literal">ER_ORDER_WITH_PROC</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't use ORDER clause with this procedure
    </p></li><li class="listitem"><p><a name="error_er_logging_prohibit_changing_of"></a>
      <a class="indexterm" name="idm46734190687280"></a>

      <a class="indexterm" name="idm46734190686272"></a>

      Error number: <code class="literal">1387</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_logging_prohibit_changing_of"><code class="literal">ER_LOGGING_PROHIBIT_CHANGING_OF</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Binary logging and replication forbid changing the global
      server %s
    </p></li><li class="listitem"><p><a name="error_er_no_file_mapping"></a>
      <a class="indexterm" name="idm46734190681136"></a>

      <a class="indexterm" name="idm46734190680128"></a>

      Error number: <code class="literal">1388</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_file_mapping"><code class="literal">ER_NO_FILE_MAPPING</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can't map file: %s, errno: %d
    </p></li><li class="listitem"><p><a name="error_er_wrong_magic"></a>
      <a class="indexterm" name="idm46734190675104"></a>

      <a class="indexterm" name="idm46734190674096"></a>

      Error number: <code class="literal">1389</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_magic"><code class="literal">ER_WRONG_MAGIC</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Wrong magic in %s
    </p></li><li class="listitem"><p><a name="error_er_ps_many_param"></a>
      <a class="indexterm" name="idm46734190669072"></a>

      <a class="indexterm" name="idm46734190668064"></a>

      Error number: <code class="literal">1390</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_ps_many_param"><code class="literal">ER_PS_MANY_PARAM</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Prepared statement contains too many placeholders
    </p></li><li class="listitem"><p><a name="error_er_key_part_0"></a>
      <a class="indexterm" name="idm46734190662960"></a>

      <a class="indexterm" name="idm46734190661952"></a>

      Error number: <code class="literal">1391</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_key_part_0"><code class="literal">ER_KEY_PART_0</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Key part '%s' length cannot be 0
    </p></li><li class="listitem"><p><a name="error_er_view_checksum"></a>
      <a class="indexterm" name="idm46734190656928"></a>

      <a class="indexterm" name="idm46734190655920"></a>

      Error number: <code class="literal">1392</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_checksum"><code class="literal">ER_VIEW_CHECKSUM</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: View text checksum failed
    </p></li><li class="listitem"><p><a name="error_er_view_multiupdate"></a>
      <a class="indexterm" name="idm46734190650896"></a>

      <a class="indexterm" name="idm46734190649888"></a>

      Error number: <code class="literal">1393</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_multiupdate"><code class="literal">ER_VIEW_MULTIUPDATE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Can not modify more than one base table through a join
      view '%s.%s'
    </p></li><li class="listitem"><p><a name="error_er_view_no_insert_field_list"></a>
      <a class="indexterm" name="idm46734190644752"></a>

      <a class="indexterm" name="idm46734190643744"></a>

      Error number: <code class="literal">1394</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_no_insert_field_list"><code class="literal">ER_VIEW_NO_INSERT_FIELD_LIST</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Can not insert into join view '%s.%s' without fields list
    </p></li><li class="listitem"><p><a name="error_er_view_delete_merge_view"></a>
      <a class="indexterm" name="idm46734190638624"></a>

      <a class="indexterm" name="idm46734190637616"></a>

      Error number: <code class="literal">1395</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_delete_merge_view"><code class="literal">ER_VIEW_DELETE_MERGE_VIEW</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Can not delete from join view '%s.%s'
    </p></li><li class="listitem"><p><a name="error_er_cannot_user"></a>
      <a class="indexterm" name="idm46734190632512"></a>

      <a class="indexterm" name="idm46734190631504"></a>

      Error number: <code class="literal">1396</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cannot_user"><code class="literal">ER_CANNOT_USER</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Operation %s failed for %s
    </p></li><li class="listitem"><p><a name="error_er_xaer_nota"></a>
      <a class="indexterm" name="idm46734190626480"></a>

      <a class="indexterm" name="idm46734190625472"></a>

      Error number: <code class="literal">1397</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_xaer_nota"><code class="literal">ER_XAER_NOTA</code></a>; SQLSTATE:
      <code class="literal">XAE04</code>
    </p><p>
      Message: XAER_NOTA: Unknown XID
    </p></li><li class="listitem"><p><a name="error_er_xaer_inval"></a>
      <a class="indexterm" name="idm46734190620448"></a>

      <a class="indexterm" name="idm46734190619440"></a>

      Error number: <code class="literal">1398</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_xaer_inval"><code class="literal">ER_XAER_INVAL</code></a>; SQLSTATE:
      <code class="literal">XAE05</code>
    </p><p>
      Message: XAER_INVAL: Invalid arguments (or unsupported command)
    </p></li><li class="listitem"><p><a name="error_er_xaer_rmfail"></a>
      <a class="indexterm" name="idm46734190614320"></a>

      <a class="indexterm" name="idm46734190613312"></a>

      Error number: <code class="literal">1399</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_xaer_rmfail"><code class="literal">ER_XAER_RMFAIL</code></a>; SQLSTATE:
      <code class="literal">XAE07</code>
    </p><p>
      Message: XAER_RMFAIL: The command cannot be executed when global
      transaction is in the %s state
    </p></li><li class="listitem"><p><a name="error_er_xaer_outside"></a>
      <a class="indexterm" name="idm46734190608160"></a>

      <a class="indexterm" name="idm46734190607152"></a>

      Error number: <code class="literal">1400</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_xaer_outside"><code class="literal">ER_XAER_OUTSIDE</code></a>; SQLSTATE:
      <code class="literal">XAE09</code>
    </p><p>
      Message: XAER_OUTSIDE: Some work is done outside global
      transaction
    </p></li><li class="listitem"><p><a name="error_er_xaer_rmerr"></a>
      <a class="indexterm" name="idm46734190602032"></a>

      <a class="indexterm" name="idm46734190601024"></a>

      Error number: <code class="literal">1401</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_xaer_rmerr"><code class="literal">ER_XAER_RMERR</code></a>; SQLSTATE:
      <code class="literal">XAE03</code>
    </p><p>
      Message: XAER_RMERR: Fatal error occurred in the transaction
      branch - check your data for consistency
    </p></li><li class="listitem"><p><a name="error_er_xa_rbrollback"></a>
      <a class="indexterm" name="idm46734190595872"></a>

      <a class="indexterm" name="idm46734190594864"></a>

      Error number: <code class="literal">1402</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_xa_rbrollback"><code class="literal">ER_XA_RBROLLBACK</code></a>; SQLSTATE:
      <code class="literal">XA100</code>
    </p><p>
      Message: XA_RBROLLBACK: Transaction branch was rolled back
    </p></li><li class="listitem"><p><a name="error_er_nonexisting_proc_grant"></a>
      <a class="indexterm" name="idm46734190589760"></a>

      <a class="indexterm" name="idm46734190588752"></a>

      Error number: <code class="literal">1403</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_nonexisting_proc_grant"><code class="literal">ER_NONEXISTING_PROC_GRANT</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: There is no such grant defined for user '%s' on host '%s'
      on routine '%s'
    </p></li><li class="listitem"><p><a name="error_er_proc_auto_grant_fail"></a>
      <a class="indexterm" name="idm46734190583616"></a>

      <a class="indexterm" name="idm46734190582608"></a>

      Error number: <code class="literal">1404</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_proc_auto_grant_fail"><code class="literal">ER_PROC_AUTO_GRANT_FAIL</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Failed to grant EXECUTE and ALTER ROUTINE privileges
    </p></li><li class="listitem"><p><a name="error_er_proc_auto_revoke_fail"></a>
      <a class="indexterm" name="idm46734190577488"></a>

      <a class="indexterm" name="idm46734190576480"></a>

      Error number: <code class="literal">1405</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_proc_auto_revoke_fail"><code class="literal">ER_PROC_AUTO_REVOKE_FAIL</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Failed to revoke all privileges to dropped routine
    </p></li><li class="listitem"><p><a name="error_er_data_too_long"></a>
      <a class="indexterm" name="idm46734190571376"></a>

      <a class="indexterm" name="idm46734190570368"></a>

      Error number: <code class="literal">1406</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_data_too_long"><code class="literal">ER_DATA_TOO_LONG</code></a>; SQLSTATE:
      <code class="literal">22001</code>
    </p><p>
      Message: Data too long for column '%s' at row %ld
    </p></li><li class="listitem"><p><a name="error_er_sp_bad_sqlstate"></a>
      <a class="indexterm" name="idm46734190565264"></a>

      <a class="indexterm" name="idm46734190564256"></a>

      Error number: <code class="literal">1407</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_bad_sqlstate"><code class="literal">ER_SP_BAD_SQLSTATE</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Bad SQLSTATE: '%s'
    </p></li><li class="listitem"><p><a name="error_er_startup"></a>
      <a class="indexterm" name="idm46734190559232"></a>

      <a class="indexterm" name="idm46734190558224"></a>

      Error number: <code class="literal">1408</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_startup"><code class="literal">ER_STARTUP</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: %s: ready for connections. Version: '%s' socket: '%s'
      port: %d %s
    </p></li><li class="listitem"><p><a name="error_er_load_from_fixed_size_rows_to_var"></a>
      <a class="indexterm" name="idm46734190553088"></a>

      <a class="indexterm" name="idm46734190552080"></a>

      Error number: <code class="literal">1409</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_load_from_fixed_size_rows_to_var"><code class="literal">ER_LOAD_FROM_FIXED_SIZE_ROWS_TO_VAR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Can't load value from file with fixed size rows to
      variable
    </p></li><li class="listitem"><p><a name="error_er_cant_create_user_with_grant"></a>
      <a class="indexterm" name="idm46734190546960"></a>

      <a class="indexterm" name="idm46734190545952"></a>

      Error number: <code class="literal">1410</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_create_user_with_grant"><code class="literal">ER_CANT_CREATE_USER_WITH_GRANT</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: You are not allowed to create a user with GRANT
    </p></li><li class="listitem"><p><a name="error_er_wrong_value_for_type"></a>
      <a class="indexterm" name="idm46734190540848"></a>

      <a class="indexterm" name="idm46734190539840"></a>

      Error number: <code class="literal">1411</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_value_for_type"><code class="literal">ER_WRONG_VALUE_FOR_TYPE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Incorrect %s value: '%s' for function %s
    </p></li><li class="listitem"><p><a name="error_er_table_def_changed"></a>
      <a class="indexterm" name="idm46734190534736"></a>

      <a class="indexterm" name="idm46734190533728"></a>

      Error number: <code class="literal">1412</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_def_changed"><code class="literal">ER_TABLE_DEF_CHANGED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Table definition has changed, please retry transaction
    </p></li><li class="listitem"><p><a name="error_er_sp_dup_handler"></a>
      <a class="indexterm" name="idm46734190528608"></a>

      <a class="indexterm" name="idm46734190527600"></a>

      Error number: <code class="literal">1413</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_dup_handler"><code class="literal">ER_SP_DUP_HANDLER</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Duplicate handler declared in the same block
    </p></li><li class="listitem"><p><a name="error_er_sp_not_var_arg"></a>
      <a class="indexterm" name="idm46734190522496"></a>

      <a class="indexterm" name="idm46734190521488"></a>

      Error number: <code class="literal">1414</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_not_var_arg"><code class="literal">ER_SP_NOT_VAR_ARG</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: OUT or INOUT argument %d for routine %s is not a variable
      or NEW pseudo-variable in BEFORE trigger
    </p></li><li class="listitem"><p><a name="error_er_sp_no_retset"></a>
      <a class="indexterm" name="idm46734190516320"></a>

      <a class="indexterm" name="idm46734190515312"></a>

      Error number: <code class="literal">1415</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_no_retset"><code class="literal">ER_SP_NO_RETSET</code></a>; SQLSTATE:
      <code class="literal">0A000</code>
    </p><p>
      Message: Not allowed to return a result set from a %s
    </p></li><li class="listitem"><p><a name="error_er_cant_create_geometry_object"></a>
      <a class="indexterm" name="idm46734190510208"></a>

      <a class="indexterm" name="idm46734190509200"></a>

      Error number: <code class="literal">1416</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_create_geometry_object"><code class="literal">ER_CANT_CREATE_GEOMETRY_OBJECT</code></a>;
      SQLSTATE: <code class="literal">22003</code>
    </p><p>
      Message: Cannot get geometry object from data you send to the
      GEOMETRY field
    </p></li><li class="listitem"><p><a name="error_er_failed_routine_break_binlog"></a>
      <a class="indexterm" name="idm46734190504064"></a>

      <a class="indexterm" name="idm46734190503056"></a>

      Error number: <code class="literal">1417</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_failed_routine_break_binlog"><code class="literal">ER_FAILED_ROUTINE_BREAK_BINLOG</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: A routine failed and has neither NO SQL nor READS SQL
      DATA in its declaration and binary logging is enabled; if
      non-transactional tables were updated, the binary log will miss
      their changes
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_routine"></a>
      <a class="indexterm" name="idm46734190497792"></a>

      <a class="indexterm" name="idm46734190496784"></a>

      Error number: <code class="literal">1418</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_routine"><code class="literal">ER_BINLOG_UNSAFE_ROUTINE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: This function has none of DETERMINISTIC, NO SQL, or READS
      SQL DATA in its declaration and binary logging is enabled (you
      *might* want to use the less safe log_bin_trust_function_creators
      variable)
    </p></li><li class="listitem"><p><a name="error_er_binlog_create_routine_need_super"></a>
      <a class="indexterm" name="idm46734190491504"></a>

      <a class="indexterm" name="idm46734190490496"></a>

      Error number: <code class="literal">1419</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_create_routine_need_super"><code class="literal">ER_BINLOG_CREATE_ROUTINE_NEED_SUPER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: You do not have the SUPER privilege and binary logging is
      enabled (you *might* want to use the less safe
      log_bin_trust_function_creators variable)
    </p></li><li class="listitem"><p><a name="error_er_exec_stmt_with_open_cursor"></a>
      <a class="indexterm" name="idm46734190485280"></a>

      <a class="indexterm" name="idm46734190484272"></a>

      Error number: <code class="literal">1420</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_exec_stmt_with_open_cursor"><code class="literal">ER_EXEC_STMT_WITH_OPEN_CURSOR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: You can't execute a prepared statement which has an open
      cursor associated with it. Reset the statement to re-execute it.
    </p></li><li class="listitem"><p><a name="error_er_stmt_has_no_open_cursor"></a>
      <a class="indexterm" name="idm46734190479088"></a>

      <a class="indexterm" name="idm46734190478080"></a>

      Error number: <code class="literal">1421</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_stmt_has_no_open_cursor"><code class="literal">ER_STMT_HAS_NO_OPEN_CURSOR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The statement (%lu) has no open cursor.
    </p></li><li class="listitem"><p><a name="error_er_commit_not_allowed_in_sf_or_trg"></a>
      <a class="indexterm" name="idm46734190472976"></a>

      <a class="indexterm" name="idm46734190471968"></a>

      Error number: <code class="literal">1422</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_commit_not_allowed_in_sf_or_trg"><code class="literal">ER_COMMIT_NOT_ALLOWED_IN_SF_OR_TRG</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Explicit or implicit commit is not allowed in stored
      function or trigger.
    </p></li><li class="listitem"><p><a name="error_er_no_default_for_view_field"></a>
      <a class="indexterm" name="idm46734190466832"></a>

      <a class="indexterm" name="idm46734190465824"></a>

      Error number: <code class="literal">1423</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_default_for_view_field"><code class="literal">ER_NO_DEFAULT_FOR_VIEW_FIELD</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Field of view '%s.%s' underlying table doesn't have a
      default value
    </p></li><li class="listitem"><p><a name="error_er_sp_no_recursion"></a>
      <a class="indexterm" name="idm46734190460688"></a>

      <a class="indexterm" name="idm46734190459680"></a>

      Error number: <code class="literal">1424</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_no_recursion"><code class="literal">ER_SP_NO_RECURSION</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Recursive stored functions and triggers are not allowed.
    </p></li><li class="listitem"><p><a name="error_er_too_big_scale"></a>
      <a class="indexterm" name="idm46734190454560"></a>

      <a class="indexterm" name="idm46734190453552"></a>

      Error number: <code class="literal">1425</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_big_scale"><code class="literal">ER_TOO_BIG_SCALE</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Too big scale %d specified for column '%s'. Maximum is
      %lu.
    </p></li><li class="listitem"><p><a name="error_er_too_big_precision"></a>
      <a class="indexterm" name="idm46734190448432"></a>

      <a class="indexterm" name="idm46734190447424"></a>

      Error number: <code class="literal">1426</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_big_precision"><code class="literal">ER_TOO_BIG_PRECISION</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Too-big precision %d specified for '%s'. Maximum is %lu.
    </p></li><li class="listitem"><p><a name="error_er_m_bigger_than_d"></a>
      <a class="indexterm" name="idm46734190442304"></a>

      <a class="indexterm" name="idm46734190441296"></a>

      Error number: <code class="literal">1427</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_m_bigger_than_d"><code class="literal">ER_M_BIGGER_THAN_D</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: For float(M,D), double(M,D) or decimal(M,D), M must be
      &gt;= D (column '%s').
    </p></li><li class="listitem"><p><a name="error_er_wrong_lock_of_system_table"></a>
      <a class="indexterm" name="idm46734190436096"></a>

      <a class="indexterm" name="idm46734190435088"></a>

      Error number: <code class="literal">1428</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_lock_of_system_table"><code class="literal">ER_WRONG_LOCK_OF_SYSTEM_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: You can't combine write-locking of system tables with
      other tables or lock types
    </p></li><li class="listitem"><p><a name="error_er_connect_to_foreign_data_source"></a>
      <a class="indexterm" name="idm46734190429936"></a>

      <a class="indexterm" name="idm46734190428928"></a>

      Error number: <code class="literal">1429</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_connect_to_foreign_data_source"><code class="literal">ER_CONNECT_TO_FOREIGN_DATA_SOURCE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Unable to connect to foreign data source: %s
    </p></li><li class="listitem"><p><a name="error_er_query_on_foreign_data_source"></a>
      <a class="indexterm" name="idm46734190423824"></a>

      <a class="indexterm" name="idm46734190422816"></a>

      Error number: <code class="literal">1430</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_query_on_foreign_data_source"><code class="literal">ER_QUERY_ON_FOREIGN_DATA_SOURCE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: There was a problem processing the query on the foreign
      data source. Data source error: %s
    </p></li><li class="listitem"><p><a name="error_er_foreign_data_source_doesnt_exist"></a>
      <a class="indexterm" name="idm46734190417664"></a>

      <a class="indexterm" name="idm46734190416656"></a>

      Error number: <code class="literal">1431</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_foreign_data_source_doesnt_exist"><code class="literal">ER_FOREIGN_DATA_SOURCE_DOESNT_EXIST</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The foreign data source you are trying to reference does
      not exist. Data source error: %s
    </p></li><li class="listitem"><p><a name="error_er_foreign_data_string_invalid_cant_create"></a>
      <a class="indexterm" name="idm46734190411504"></a>

      <a class="indexterm" name="idm46734190410496"></a>

      Error number: <code class="literal">1432</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_foreign_data_string_invalid_cant_create"><code class="literal">ER_FOREIGN_DATA_STRING_INVALID_CANT_CREATE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Can't create federated table. The data source connection
      string '%s' is not in the correct format
    </p></li><li class="listitem"><p><a name="error_er_foreign_data_string_invalid"></a>
      <a class="indexterm" name="idm46734190405328"></a>

      <a class="indexterm" name="idm46734190404320"></a>

      Error number: <code class="literal">1433</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_foreign_data_string_invalid"><code class="literal">ER_FOREIGN_DATA_STRING_INVALID</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The data source connection string '%s' is not in the
      correct format
    </p></li><li class="listitem"><p><a name="error_er_cant_create_federated_table"></a>
      <a class="indexterm" name="idm46734190399184"></a>

      <a class="indexterm" name="idm46734190398176"></a>

      Error number: <code class="literal">1434</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_create_federated_table"><code class="literal">ER_CANT_CREATE_FEDERATED_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Can't create federated table. Foreign data src error: %s
    </p></li><li class="listitem"><p><a name="error_er_trg_in_wrong_schema"></a>
      <a class="indexterm" name="idm46734190393056"></a>

      <a class="indexterm" name="idm46734190392048"></a>

      Error number: <code class="literal">1435</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_trg_in_wrong_schema"><code class="literal">ER_TRG_IN_WRONG_SCHEMA</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Trigger in wrong schema
    </p></li><li class="listitem"><p><a name="error_er_stack_overrun_need_more"></a>
      <a class="indexterm" name="idm46734190387024"></a>

      <a class="indexterm" name="idm46734190386016"></a>

      Error number: <code class="literal">1436</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_stack_overrun_need_more"><code class="literal">ER_STACK_OVERRUN_NEED_MORE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Thread stack overrun: %ld bytes used of a %ld byte stack,
      and %ld bytes needed. Use 'mysqld --thread_stack=#' to specify a
      bigger stack.
    </p></li><li class="listitem"><p><a name="error_er_too_long_body"></a>
      <a class="indexterm" name="idm46734190380800"></a>

      <a class="indexterm" name="idm46734190379792"></a>

      Error number: <code class="literal">1437</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_long_body"><code class="literal">ER_TOO_LONG_BODY</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Routine body for '%s' is too long
    </p></li><li class="listitem"><p><a name="error_er_warn_cant_drop_default_keycache"></a>
      <a class="indexterm" name="idm46734190374768"></a>

      <a class="indexterm" name="idm46734190373760"></a>

      Error number: <code class="literal">1438</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_cant_drop_default_keycache"><code class="literal">ER_WARN_CANT_DROP_DEFAULT_KEYCACHE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot drop default keycache
    </p></li><li class="listitem"><p><a name="error_er_too_big_displaywidth"></a>
      <a class="indexterm" name="idm46734190368736"></a>

      <a class="indexterm" name="idm46734190367728"></a>

      Error number: <code class="literal">1439</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_big_displaywidth"><code class="literal">ER_TOO_BIG_DISPLAYWIDTH</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Display width out of range for column '%s' (max = %lu)
    </p></li><li class="listitem"><p><a name="error_er_xaer_dupid"></a>
      <a class="indexterm" name="idm46734190362608"></a>

      <a class="indexterm" name="idm46734190361600"></a>

      Error number: <code class="literal">1440</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_xaer_dupid"><code class="literal">ER_XAER_DUPID</code></a>; SQLSTATE:
      <code class="literal">XAE08</code>
    </p><p>
      Message: XAER_DUPID: The XID already exists
    </p></li><li class="listitem"><p><a name="error_er_datetime_function_overflow"></a>
      <a class="indexterm" name="idm46734190356576"></a>

      <a class="indexterm" name="idm46734190355568"></a>

      Error number: <code class="literal">1441</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_datetime_function_overflow"><code class="literal">ER_DATETIME_FUNCTION_OVERFLOW</code></a>;
      SQLSTATE: <code class="literal">22008</code>
    </p><p>
      Message: Datetime function: %s field overflow
    </p></li><li class="listitem"><p><a name="error_er_cant_update_used_table_in_sf_or_trg"></a>
      <a class="indexterm" name="idm46734190350464"></a>

      <a class="indexterm" name="idm46734190349456"></a>

      Error number: <code class="literal">1442</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_update_used_table_in_sf_or_trg"><code class="literal">ER_CANT_UPDATE_USED_TABLE_IN_SF_OR_TRG</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Can't update table '%s' in stored function/trigger
      because it is already used by statement which invoked this stored
      function/trigger.
    </p></li><li class="listitem"><p><a name="error_er_view_prevent_update"></a>
      <a class="indexterm" name="idm46734190344256"></a>

      <a class="indexterm" name="idm46734190343248"></a>

      Error number: <code class="literal">1443</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_prevent_update"><code class="literal">ER_VIEW_PREVENT_UPDATE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The definition of table '%s' prevents operation %s on
      table '%s'.
    </p></li><li class="listitem"><p><a name="error_er_ps_no_recursion"></a>
      <a class="indexterm" name="idm46734190338112"></a>

      <a class="indexterm" name="idm46734190337104"></a>

      Error number: <code class="literal">1444</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_ps_no_recursion"><code class="literal">ER_PS_NO_RECURSION</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The prepared statement contains a stored routine call
      that refers to that same statement. It's not allowed to execute a
      prepared statement in such a recursive manner
    </p></li><li class="listitem"><p><a name="error_er_sp_cant_set_autocommit"></a>
      <a class="indexterm" name="idm46734190331872"></a>

      <a class="indexterm" name="idm46734190330864"></a>

      Error number: <code class="literal">1445</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_cant_set_autocommit"><code class="literal">ER_SP_CANT_SET_AUTOCOMMIT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Not allowed to set autocommit from a stored function or
      trigger
    </p></li><li class="listitem"><p><a name="error_er_malformed_definer"></a>
      <a class="indexterm" name="idm46734190325728"></a>

      <a class="indexterm" name="idm46734190324720"></a>

      Error number: <code class="literal">1446</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_malformed_definer"><code class="literal">ER_MALFORMED_DEFINER</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Definer is not fully qualified
    </p></li><li class="listitem"><p><a name="error_er_view_frm_no_user"></a>
      <a class="indexterm" name="idm46734190319696"></a>

      <a class="indexterm" name="idm46734190318688"></a>

      Error number: <code class="literal">1447</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_frm_no_user"><code class="literal">ER_VIEW_FRM_NO_USER</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: View '%s'.'%s' has no definer information (old table
      format). Current user is used as definer. Please recreate the
      view!
    </p></li><li class="listitem"><p><a name="error_er_view_other_user"></a>
      <a class="indexterm" name="idm46734190313488"></a>

      <a class="indexterm" name="idm46734190312480"></a>

      Error number: <code class="literal">1448</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_other_user"><code class="literal">ER_VIEW_OTHER_USER</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: You need the SUPER privilege for creation view with
      '%s'@'%s' definer
    </p></li><li class="listitem"><p><a name="error_er_no_such_user"></a>
      <a class="indexterm" name="idm46734190307344"></a>

      <a class="indexterm" name="idm46734190306336"></a>

      Error number: <code class="literal">1449</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_such_user"><code class="literal">ER_NO_SUCH_USER</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The user specified as a definer ('%s'@'%s') does not
      exist
    </p></li><li class="listitem"><p><a name="error_er_forbid_schema_change"></a>
      <a class="indexterm" name="idm46734190301216"></a>

      <a class="indexterm" name="idm46734190300208"></a>

      Error number: <code class="literal">1450</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_forbid_schema_change"><code class="literal">ER_FORBID_SCHEMA_CHANGE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Changing schema from '%s' to '%s' is not allowed.
    </p></li><li class="listitem"><p><a name="error_er_row_is_referenced_2"></a>
      <a class="indexterm" name="idm46734190295104"></a>

      <a class="indexterm" name="idm46734190294096"></a>

      Error number: <code class="literal">1451</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_row_is_referenced_2"><code class="literal">ER_ROW_IS_REFERENCED_2</code></a>; SQLSTATE:
      <code class="literal">23000</code>
    </p><p>
      Message: Cannot delete or update a parent row: a foreign key
      constraint fails (%s)
    </p><p>
      <code class="literal">InnoDB</code> reports this error when you try to
      delete a parent row that has children, and a
      <a class="link" href="glossary.html#glos_foreign_key_constraint" title="FOREIGN KEY constraint">foreign key
      constraint</a> fails. Delete the children first.
    </p></li><li class="listitem"><p><a name="error_er_no_referenced_row_2"></a>
      <a class="indexterm" name="idm46734190287216"></a>

      <a class="indexterm" name="idm46734190286208"></a>

      Error number: <code class="literal">1452</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_referenced_row_2"><code class="literal">ER_NO_REFERENCED_ROW_2</code></a>; SQLSTATE:
      <code class="literal">23000</code>
    </p><p>
      Message: Cannot add or update a child row: a foreign key
      constraint fails (%s)
    </p><p>
      <code class="literal">InnoDB</code> reports this error when you try to add a
      row but there is no parent row, and a
      <a class="link" href="glossary.html#glos_foreign_key_constraint" title="FOREIGN KEY constraint">foreign key
      constraint</a> fails. Add the parent row first.
    </p></li><li class="listitem"><p><a name="error_er_sp_bad_var_shadow"></a>
      <a class="indexterm" name="idm46734190279328"></a>

      <a class="indexterm" name="idm46734190278320"></a>

      Error number: <code class="literal">1453</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_bad_var_shadow"><code class="literal">ER_SP_BAD_VAR_SHADOW</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Variable '%s' must be quoted with `...`, or renamed
    </p></li><li class="listitem"><p><a name="error_er_trg_no_definer"></a>
      <a class="indexterm" name="idm46734190273200"></a>

      <a class="indexterm" name="idm46734190272192"></a>

      Error number: <code class="literal">1454</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_trg_no_definer"><code class="literal">ER_TRG_NO_DEFINER</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: No definer attribute for trigger '%s'.'%s'. The trigger
      will be activated under the authorization of the invoker, which
      may have insufficient privileges. Please recreate the trigger.
    </p></li><li class="listitem"><p><a name="error_er_old_file_format"></a>
      <a class="indexterm" name="idm46734190266944"></a>

      <a class="indexterm" name="idm46734190265936"></a>

      Error number: <code class="literal">1455</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_old_file_format"><code class="literal">ER_OLD_FILE_FORMAT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: '%s' has an old format, you should re-create the '%s'
      object(s)
    </p></li><li class="listitem"><p><a name="error_er_sp_recursion_limit"></a>
      <a class="indexterm" name="idm46734190260800"></a>

      <a class="indexterm" name="idm46734190259792"></a>

      Error number: <code class="literal">1456</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_recursion_limit"><code class="literal">ER_SP_RECURSION_LIMIT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Recursive limit %d (as set by the max_sp_recursion_depth
      variable) was exceeded for routine %s
    </p></li><li class="listitem"><p><a name="error_er_sp_proc_table_corrupt"></a>
      <a class="indexterm" name="idm46734190254624"></a>

      <a class="indexterm" name="idm46734190253616"></a>

      Error number: <code class="literal">1457</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_proc_table_corrupt"><code class="literal">ER_SP_PROC_TABLE_CORRUPT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Failed to load routine %s. The table mysql.proc is
      missing, corrupt, or contains bad data (internal code %d)
    </p></li><li class="listitem"><p><a name="error_er_sp_wrong_name"></a>
      <a class="indexterm" name="idm46734190248448"></a>

      <a class="indexterm" name="idm46734190247440"></a>

      Error number: <code class="literal">1458</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_wrong_name"><code class="literal">ER_SP_WRONG_NAME</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Incorrect routine name '%s'
    </p></li><li class="listitem"><p><a name="error_er_table_needs_upgrade"></a>
      <a class="indexterm" name="idm46734190242416"></a>

      <a class="indexterm" name="idm46734190241408"></a>

      Error number: <code class="literal">1459</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_needs_upgrade"><code class="literal">ER_TABLE_NEEDS_UPGRADE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Table upgrade required. Please do "REPAIR TABLE `%s`" or
      dump/reload to fix it!
    </p></li><li class="listitem"><p><a name="error_er_sp_no_aggregate"></a>
      <a class="indexterm" name="idm46734190236256"></a>

      <a class="indexterm" name="idm46734190235248"></a>

      Error number: <code class="literal">1460</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sp_no_aggregate"><code class="literal">ER_SP_NO_AGGREGATE</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: AGGREGATE is not supported for stored functions
    </p></li><li class="listitem"><p><a name="error_er_max_prepared_stmt_count_reached"></a>
      <a class="indexterm" name="idm46734190230144"></a>

      <a class="indexterm" name="idm46734190229136"></a>

      Error number: <code class="literal">1461</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_max_prepared_stmt_count_reached"><code class="literal">ER_MAX_PREPARED_STMT_COUNT_REACHED</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Can't create more than max_prepared_stmt_count statements
      (current value: %lu)
    </p></li><li class="listitem"><p><a name="error_er_view_recursive"></a>
      <a class="indexterm" name="idm46734190223984"></a>

      <a class="indexterm" name="idm46734190222976"></a>

      Error number: <code class="literal">1462</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_recursive"><code class="literal">ER_VIEW_RECURSIVE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: `%s`.`%s` contains view recursion
    </p></li><li class="listitem"><p><a name="error_er_non_grouping_field_used"></a>
      <a class="indexterm" name="idm46734190217952"></a>

      <a class="indexterm" name="idm46734190216944"></a>

      Error number: <code class="literal">1463</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_non_grouping_field_used"><code class="literal">ER_NON_GROUPING_FIELD_USED</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Non-grouping field '%s' is used in %s clause
    </p></li><li class="listitem"><p><a name="error_er_table_cant_handle_spkeys"></a>
      <a class="indexterm" name="idm46734190211840"></a>

      <a class="indexterm" name="idm46734190210832"></a>

      Error number: <code class="literal">1464</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_cant_handle_spkeys"><code class="literal">ER_TABLE_CANT_HANDLE_SPKEYS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The used table type doesn't support SPATIAL indexes
    </p></li><li class="listitem"><p><a name="error_er_no_triggers_on_system_schema"></a>
      <a class="indexterm" name="idm46734190205712"></a>

      <a class="indexterm" name="idm46734190204704"></a>

      Error number: <code class="literal">1465</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_triggers_on_system_schema"><code class="literal">ER_NO_TRIGGERS_ON_SYSTEM_SCHEMA</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Triggers can not be created on system tables
    </p></li><li class="listitem"><p><a name="error_er_removed_spaces"></a>
      <a class="indexterm" name="idm46734190199600"></a>

      <a class="indexterm" name="idm46734190198592"></a>

      Error number: <code class="literal">1466</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_removed_spaces"><code class="literal">ER_REMOVED_SPACES</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Leading spaces are removed from name '%s'
    </p></li><li class="listitem"><p><a name="error_er_autoinc_read_failed"></a>
      <a class="indexterm" name="idm46734190193488"></a>

      <a class="indexterm" name="idm46734190192480"></a>

      Error number: <code class="literal">1467</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_autoinc_read_failed"><code class="literal">ER_AUTOINC_READ_FAILED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Failed to read auto-increment value from storage engine
    </p></li><li class="listitem"><p><a name="error_er_username"></a>
      <a class="indexterm" name="idm46734190187360"></a>

      <a class="indexterm" name="idm46734190186352"></a>

      Error number: <code class="literal">1468</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_username"><code class="literal">ER_USERNAME</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: user name
    </p></li><li class="listitem"><p><a name="error_er_hostname"></a>
      <a class="indexterm" name="idm46734190181328"></a>

      <a class="indexterm" name="idm46734190180320"></a>

      Error number: <code class="literal">1469</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_hostname"><code class="literal">ER_HOSTNAME</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: host name
    </p></li><li class="listitem"><p><a name="error_er_wrong_string_length"></a>
      <a class="indexterm" name="idm46734190175296"></a>

      <a class="indexterm" name="idm46734190174288"></a>

      Error number: <code class="literal">1470</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_string_length"><code class="literal">ER_WRONG_STRING_LENGTH</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: String '%s' is too long for %s (should be no longer than
      %d)
    </p></li><li class="listitem"><p><a name="error_er_non_insertable_table"></a>
      <a class="indexterm" name="idm46734190169168"></a>

      <a class="indexterm" name="idm46734190168160"></a>

      Error number: <code class="literal">1471</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_non_insertable_table"><code class="literal">ER_NON_INSERTABLE_TABLE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The target table %s of the %s is not insertable-into
    </p></li><li class="listitem"><p><a name="error_er_admin_wrong_mrg_table"></a>
      <a class="indexterm" name="idm46734190163040"></a>

      <a class="indexterm" name="idm46734190162032"></a>

      Error number: <code class="literal">1472</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_admin_wrong_mrg_table"><code class="literal">ER_ADMIN_WRONG_MRG_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Table '%s' is differently defined or of non-MyISAM type
      or doesn't exist
    </p></li><li class="listitem"><p><a name="error_er_too_high_level_of_nesting_for_select"></a>
      <a class="indexterm" name="idm46734190156896"></a>

      <a class="indexterm" name="idm46734190155888"></a>

      Error number: <code class="literal">1473</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_high_level_of_nesting_for_select"><code class="literal">ER_TOO_HIGH_LEVEL_OF_NESTING_FOR_SELECT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Too high level of nesting for select
    </p></li><li class="listitem"><p><a name="error_er_name_becomes_empty"></a>
      <a class="indexterm" name="idm46734190150784"></a>

      <a class="indexterm" name="idm46734190149776"></a>

      Error number: <code class="literal">1474</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_name_becomes_empty"><code class="literal">ER_NAME_BECOMES_EMPTY</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Name '%s' has become ''
    </p></li><li class="listitem"><p><a name="error_er_ambiguous_field_term"></a>
      <a class="indexterm" name="idm46734190144752"></a>

      <a class="indexterm" name="idm46734190143744"></a>

      Error number: <code class="literal">1475</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_ambiguous_field_term"><code class="literal">ER_AMBIGUOUS_FIELD_TERM</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: First character of the FIELDS TERMINATED string is
      ambiguous; please use non-optional and non-empty FIELDS ENCLOSED
      BY
    </p></li><li class="listitem"><p><a name="error_er_foreign_server_exists"></a>
      <a class="indexterm" name="idm46734190138560"></a>

      <a class="indexterm" name="idm46734190137552"></a>

      Error number: <code class="literal">1476</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_foreign_server_exists"><code class="literal">ER_FOREIGN_SERVER_EXISTS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The foreign server, %s, you are trying to create already
      exists.
    </p></li><li class="listitem"><p><a name="error_er_foreign_server_doesnt_exist"></a>
      <a class="indexterm" name="idm46734190132416"></a>

      <a class="indexterm" name="idm46734190131408"></a>

      Error number: <code class="literal">1477</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_foreign_server_doesnt_exist"><code class="literal">ER_FOREIGN_SERVER_DOESNT_EXIST</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The foreign server name you are trying to reference does
      not exist. Data source error: %s
    </p></li><li class="listitem"><p><a name="error_er_illegal_ha_create_option"></a>
      <a class="indexterm" name="idm46734190126256"></a>

      <a class="indexterm" name="idm46734190125248"></a>

      Error number: <code class="literal">1478</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_illegal_ha_create_option"><code class="literal">ER_ILLEGAL_HA_CREATE_OPTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Table storage engine '%s' does not support the create
      option '%s'
    </p></li><li class="listitem"><p><a name="error_er_partition_requires_values_error"></a>
      <a class="indexterm" name="idm46734190120112"></a>

      <a class="indexterm" name="idm46734190119104"></a>

      Error number: <code class="literal">1479</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_requires_values_error"><code class="literal">ER_PARTITION_REQUIRES_VALUES_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Syntax error: %s PARTITIONING requires definition of
      VALUES %s for each partition
    </p></li><li class="listitem"><p><a name="error_er_partition_wrong_values_error"></a>
      <a class="indexterm" name="idm46734190113952"></a>

      <a class="indexterm" name="idm46734190112944"></a>

      Error number: <code class="literal">1480</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_wrong_values_error"><code class="literal">ER_PARTITION_WRONG_VALUES_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Only %s PARTITIONING can use VALUES %s in partition
      definition
    </p></li><li class="listitem"><p><a name="error_er_partition_maxvalue_error"></a>
      <a class="indexterm" name="idm46734190107808"></a>

      <a class="indexterm" name="idm46734190106800"></a>

      Error number: <code class="literal">1481</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_maxvalue_error"><code class="literal">ER_PARTITION_MAXVALUE_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: MAXVALUE can only be used in last partition definition
    </p></li><li class="listitem"><p><a name="error_er_partition_subpartition_error"></a>
      <a class="indexterm" name="idm46734190101680"></a>

      <a class="indexterm" name="idm46734190100672"></a>

      Error number: <code class="literal">1482</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_subpartition_error"><code class="literal">ER_PARTITION_SUBPARTITION_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Subpartitions can only be hash partitions and by key
    </p></li><li class="listitem"><p><a name="error_er_partition_subpart_mix_error"></a>
      <a class="indexterm" name="idm46734190095552"></a>

      <a class="indexterm" name="idm46734190094544"></a>

      Error number: <code class="literal">1483</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_subpart_mix_error"><code class="literal">ER_PARTITION_SUBPART_MIX_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Must define subpartitions on all partitions if on one
      partition
    </p></li><li class="listitem"><p><a name="error_er_partition_wrong_no_part_error"></a>
      <a class="indexterm" name="idm46734190089408"></a>

      <a class="indexterm" name="idm46734190088400"></a>

      Error number: <code class="literal">1484</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_wrong_no_part_error"><code class="literal">ER_PARTITION_WRONG_NO_PART_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Wrong number of partitions defined, mismatch with
      previous setting
    </p></li><li class="listitem"><p><a name="error_er_partition_wrong_no_subpart_error"></a>
      <a class="indexterm" name="idm46734190083264"></a>

      <a class="indexterm" name="idm46734190082256"></a>

      Error number: <code class="literal">1485</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_wrong_no_subpart_error"><code class="literal">ER_PARTITION_WRONG_NO_SUBPART_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Wrong number of subpartitions defined, mismatch with
      previous setting
    </p></li><li class="listitem"><p><a name="error_er_wrong_expr_in_partition_func_error"></a>
      <a class="indexterm" name="idm46734190077120"></a>

      <a class="indexterm" name="idm46734190076112"></a>

      Error number: <code class="literal">1486</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_expr_in_partition_func_error"><code class="literal">ER_WRONG_EXPR_IN_PARTITION_FUNC_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Constant, random or timezone-dependent expressions in
      (sub)partitioning function are not allowed
    </p></li><li class="listitem"><p><a name="error_er_no_const_expr_in_range_or_list_error"></a>
      <a class="indexterm" name="idm46734190070944"></a>

      <a class="indexterm" name="idm46734190069936"></a>

      Error number: <code class="literal">1487</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_const_expr_in_range_or_list_error"><code class="literal">ER_NO_CONST_EXPR_IN_RANGE_OR_LIST_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Expression in RANGE/LIST VALUES must be constant
    </p></li><li class="listitem"><p><a name="error_er_field_not_found_part_error"></a>
      <a class="indexterm" name="idm46734190064832"></a>

      <a class="indexterm" name="idm46734190063824"></a>

      Error number: <code class="literal">1488</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_field_not_found_part_error"><code class="literal">ER_FIELD_NOT_FOUND_PART_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Field in list of fields for partition function not found
      in table
    </p></li><li class="listitem"><p><a name="error_er_list_of_fields_only_in_hash_error"></a>
      <a class="indexterm" name="idm46734190058688"></a>

      <a class="indexterm" name="idm46734190057680"></a>

      Error number: <code class="literal">1489</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_list_of_fields_only_in_hash_error"><code class="literal">ER_LIST_OF_FIELDS_ONLY_IN_HASH_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: List of fields is only allowed in KEY partitions
    </p></li><li class="listitem"><p><a name="error_er_inconsistent_partition_info_error"></a>
      <a class="indexterm" name="idm46734190052576"></a>

      <a class="indexterm" name="idm46734190051568"></a>

      Error number: <code class="literal">1490</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_inconsistent_partition_info_error"><code class="literal">ER_INCONSISTENT_PARTITION_INFO_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The partition info in the frm file is not consistent with
      what can be written into the frm file
    </p></li><li class="listitem"><p><a name="error_er_partition_func_not_allowed_error"></a>
      <a class="indexterm" name="idm46734190046400"></a>

      <a class="indexterm" name="idm46734190045392"></a>

      Error number: <code class="literal">1491</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_func_not_allowed_error"><code class="literal">ER_PARTITION_FUNC_NOT_ALLOWED_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The %s function returns the wrong type
    </p></li><li class="listitem"><p><a name="error_er_partitions_must_be_defined_error"></a>
      <a class="indexterm" name="idm46734190040288"></a>

      <a class="indexterm" name="idm46734190039280"></a>

      Error number: <code class="literal">1492</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partitions_must_be_defined_error"><code class="literal">ER_PARTITIONS_MUST_BE_DEFINED_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: For %s partitions each partition must be defined
    </p></li><li class="listitem"><p><a name="error_er_range_not_increasing_error"></a>
      <a class="indexterm" name="idm46734190034176"></a>

      <a class="indexterm" name="idm46734190033168"></a>

      Error number: <code class="literal">1493</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_range_not_increasing_error"><code class="literal">ER_RANGE_NOT_INCREASING_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: VALUES LESS THAN value must be strictly increasing for
      each partition
    </p></li><li class="listitem"><p><a name="error_er_inconsistent_type_of_functions_error"></a>
      <a class="indexterm" name="idm46734190028032"></a>

      <a class="indexterm" name="idm46734190027024"></a>

      Error number: <code class="literal">1494</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_inconsistent_type_of_functions_error"><code class="literal">ER_INCONSISTENT_TYPE_OF_FUNCTIONS_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: VALUES value must be of same type as partition function
    </p></li><li class="listitem"><p><a name="error_er_multiple_def_const_in_list_part_error"></a>
      <a class="indexterm" name="idm46734190021904"></a>

      <a class="indexterm" name="idm46734190020896"></a>

      Error number: <code class="literal">1495</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_multiple_def_const_in_list_part_error"><code class="literal">ER_MULTIPLE_DEF_CONST_IN_LIST_PART_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Multiple definition of same constant in list partitioning
    </p></li><li class="listitem"><p><a name="error_er_partition_entry_error"></a>
      <a class="indexterm" name="idm46734190015776"></a>

      <a class="indexterm" name="idm46734190014768"></a>

      Error number: <code class="literal">1496</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_entry_error"><code class="literal">ER_PARTITION_ENTRY_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Partitioning can not be used stand-alone in query
    </p></li><li class="listitem"><p><a name="error_er_mix_handler_error"></a>
      <a class="indexterm" name="idm46734190009664"></a>

      <a class="indexterm" name="idm46734190008656"></a>

      Error number: <code class="literal">1497</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_mix_handler_error"><code class="literal">ER_MIX_HANDLER_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The mix of handlers in the partitions is not allowed in
      this version of MySQL
    </p></li><li class="listitem"><p><a name="error_er_partition_not_defined_error"></a>
      <a class="indexterm" name="idm46734190003504"></a>

      <a class="indexterm" name="idm46734190002496"></a>

      Error number: <code class="literal">1498</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_not_defined_error"><code class="literal">ER_PARTITION_NOT_DEFINED_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: For the partitioned engine it is necessary to define all
      %s
    </p></li><li class="listitem"><p><a name="error_er_too_many_partitions_error"></a>
      <a class="indexterm" name="idm46734189997376"></a>

      <a class="indexterm" name="idm46734189996368"></a>

      Error number: <code class="literal">1499</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_many_partitions_error"><code class="literal">ER_TOO_MANY_PARTITIONS_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Too many partitions (including subpartitions) were
      defined
    </p></li><li class="listitem"><p><a name="error_er_subpartition_error"></a>
      <a class="indexterm" name="idm46734189991248"></a>

      <a class="indexterm" name="idm46734189990240"></a>

      Error number: <code class="literal">1500</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_subpartition_error"><code class="literal">ER_SUBPARTITION_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: It is only possible to mix RANGE/LIST partitioning with
      HASH/KEY partitioning for subpartitioning
    </p></li><li class="listitem"><p><a name="error_er_cant_create_handler_file"></a>
      <a class="indexterm" name="idm46734189985072"></a>

      <a class="indexterm" name="idm46734189984064"></a>

      Error number: <code class="literal">1501</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_create_handler_file"><code class="literal">ER_CANT_CREATE_HANDLER_FILE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Failed to create specific handler file
    </p></li><li class="listitem"><p><a name="error_er_blob_field_in_part_func_error"></a>
      <a class="indexterm" name="idm46734189978960"></a>

      <a class="indexterm" name="idm46734189977952"></a>

      Error number: <code class="literal">1502</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_blob_field_in_part_func_error"><code class="literal">ER_BLOB_FIELD_IN_PART_FUNC_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: A BLOB field is not allowed in partition function
    </p></li><li class="listitem"><p><a name="error_er_unique_key_need_all_fields_in_pf"></a>
      <a class="indexterm" name="idm46734189972848"></a>

      <a class="indexterm" name="idm46734189971840"></a>

      Error number: <code class="literal">1503</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unique_key_need_all_fields_in_pf"><code class="literal">ER_UNIQUE_KEY_NEED_ALL_FIELDS_IN_PF</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: A %s must include all columns in the table's partitioning
      function
    </p></li><li class="listitem"><p><a name="error_er_no_parts_error"></a>
      <a class="indexterm" name="idm46734189966704"></a>

      <a class="indexterm" name="idm46734189965696"></a>

      Error number: <code class="literal">1504</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_parts_error"><code class="literal">ER_NO_PARTS_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Number of %s = 0 is not an allowed value
    </p></li><li class="listitem"><p><a name="error_er_partition_mgmt_on_nonpartitioned"></a>
      <a class="indexterm" name="idm46734189960592"></a>

      <a class="indexterm" name="idm46734189959584"></a>

      Error number: <code class="literal">1505</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_mgmt_on_nonpartitioned"><code class="literal">ER_PARTITION_MGMT_ON_NONPARTITIONED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Partition management on a not partitioned table is not
      possible
    </p></li><li class="listitem"><p><a name="error_er_foreign_key_on_partitioned"></a>
      <a class="indexterm" name="idm46734189954448"></a>

      <a class="indexterm" name="idm46734189953440"></a>

      Error number: <code class="literal">1506</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_foreign_key_on_partitioned"><code class="literal">ER_FOREIGN_KEY_ON_PARTITIONED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Foreign keys are not yet supported in conjunction with
      partitioning
    </p></li><li class="listitem"><p><a name="error_er_drop_partition_non_existent"></a>
      <a class="indexterm" name="idm46734189948304"></a>

      <a class="indexterm" name="idm46734189947296"></a>

      Error number: <code class="literal">1507</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_drop_partition_non_existent"><code class="literal">ER_DROP_PARTITION_NON_EXISTENT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Error in list of partitions to %s
    </p></li><li class="listitem"><p><a name="error_er_drop_last_partition"></a>
      <a class="indexterm" name="idm46734189942272"></a>

      <a class="indexterm" name="idm46734189941264"></a>

      Error number: <code class="literal">1508</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_drop_last_partition"><code class="literal">ER_DROP_LAST_PARTITION</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Cannot remove all partitions, use DROP TABLE instead
    </p></li><li class="listitem"><p><a name="error_er_coalesce_only_on_hash_partition"></a>
      <a class="indexterm" name="idm46734189936144"></a>

      <a class="indexterm" name="idm46734189935136"></a>

      Error number: <code class="literal">1509</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_coalesce_only_on_hash_partition"><code class="literal">ER_COALESCE_ONLY_ON_HASH_PARTITION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: COALESCE PARTITION can only be used on HASH/KEY
      partitions
    </p></li><li class="listitem"><p><a name="error_er_reorg_hash_only_on_same_no"></a>
      <a class="indexterm" name="idm46734189930016"></a>

      <a class="indexterm" name="idm46734189929008"></a>

      Error number: <code class="literal">1510</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_reorg_hash_only_on_same_no"><code class="literal">ER_REORG_HASH_ONLY_ON_SAME_NO</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: REORGANIZE PARTITION can only be used to reorganize
      partitions not to change their numbers
    </p></li><li class="listitem"><p><a name="error_er_reorg_no_param_error"></a>
      <a class="indexterm" name="idm46734189923856"></a>

      <a class="indexterm" name="idm46734189922848"></a>

      Error number: <code class="literal">1511</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_reorg_no_param_error"><code class="literal">ER_REORG_NO_PARAM_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: REORGANIZE PARTITION without parameters can only be used
      on auto-partitioned tables using HASH PARTITIONs
    </p></li><li class="listitem"><p><a name="error_er_only_on_range_list_partition"></a>
      <a class="indexterm" name="idm46734189917680"></a>

      <a class="indexterm" name="idm46734189916672"></a>

      Error number: <code class="literal">1512</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_only_on_range_list_partition"><code class="literal">ER_ONLY_ON_RANGE_LIST_PARTITION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: %s PARTITION can only be used on RANGE/LIST partitions
    </p></li><li class="listitem"><p><a name="error_er_add_partition_subpart_error"></a>
      <a class="indexterm" name="idm46734189911552"></a>

      <a class="indexterm" name="idm46734189910544"></a>

      Error number: <code class="literal">1513</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_add_partition_subpart_error"><code class="literal">ER_ADD_PARTITION_SUBPART_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Trying to Add partition(s) with wrong number of
      subpartitions
    </p></li><li class="listitem"><p><a name="error_er_add_partition_no_new_partition"></a>
      <a class="indexterm" name="idm46734189905152"></a>

      <a class="indexterm" name="idm46734189904112"></a>

      Error number: <code class="literal">1514</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_add_partition_no_new_partition"><code class="literal">ER_ADD_PARTITION_NO_NEW_PARTITION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: At least one partition must be added
    </p></li><li class="listitem"><p><a name="error_er_coalesce_partition_no_partition"></a>
      <a class="indexterm" name="idm46734189898352"></a>

      <a class="indexterm" name="idm46734189897312"></a>

      Error number: <code class="literal">1515</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_coalesce_partition_no_partition"><code class="literal">ER_COALESCE_PARTITION_NO_PARTITION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: At least one partition must be coalesced
    </p></li><li class="listitem"><p><a name="error_er_reorg_partition_not_exist"></a>
      <a class="indexterm" name="idm46734189891200"></a>

      <a class="indexterm" name="idm46734189890160"></a>

      Error number: <code class="literal">1516</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_reorg_partition_not_exist"><code class="literal">ER_REORG_PARTITION_NOT_EXIST</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: More partitions to reorganize than there are partitions
    </p></li><li class="listitem"><p><a name="error_er_same_name_partition"></a>
      <a class="indexterm" name="idm46734189884128"></a>

      <a class="indexterm" name="idm46734189883088"></a>

      Error number: <code class="literal">1517</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_same_name_partition"><code class="literal">ER_SAME_NAME_PARTITION</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Duplicate partition name %s
    </p></li><li class="listitem"><p><a name="error_er_no_binlog_error"></a>
      <a class="indexterm" name="idm46734189876992"></a>

      <a class="indexterm" name="idm46734189875952"></a>

      Error number: <code class="literal">1518</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_binlog_error"><code class="literal">ER_NO_BINLOG_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: It is not allowed to shut off binlog on this command
    </p></li><li class="listitem"><p><a name="error_er_consecutive_reorg_partitions"></a>
      <a class="indexterm" name="idm46734189869888"></a>

      <a class="indexterm" name="idm46734189868784"></a>

      Error number: <code class="literal">1519</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_consecutive_reorg_partitions"><code class="literal">ER_CONSECUTIVE_REORG_PARTITIONS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: When reorganizing a set of partitions they must be in
      consecutive order
    </p></li><li class="listitem"><p><a name="error_er_reorg_outside_range"></a>
      <a class="indexterm" name="idm46734189862720"></a>

      <a class="indexterm" name="idm46734189861680"></a>

      Error number: <code class="literal">1520</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_reorg_outside_range"><code class="literal">ER_REORG_OUTSIDE_RANGE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Reorganize of range partitions cannot change total ranges
      except for last partition where it can extend the range
    </p></li><li class="listitem"><p><a name="error_er_partition_function_failure"></a>
      <a class="indexterm" name="idm46734189855488"></a>

      <a class="indexterm" name="idm46734189854384"></a>

      Error number: <code class="literal">1521</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_function_failure"><code class="literal">ER_PARTITION_FUNCTION_FAILURE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Partition function not supported in this version for this
      handler
    </p></li><li class="listitem"><p><a name="error_er_part_state_error"></a>
      <a class="indexterm" name="idm46734189848320"></a>

      <a class="indexterm" name="idm46734189847280"></a>

      Error number: <code class="literal">1522</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_part_state_error"><code class="literal">ER_PART_STATE_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Partition state cannot be defined from CREATE/ALTER TABLE
    </p></li><li class="listitem"><p><a name="error_er_limited_part_range"></a>
      <a class="indexterm" name="idm46734189841216"></a>

      <a class="indexterm" name="idm46734189840176"></a>

      Error number: <code class="literal">1523</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_limited_part_range"><code class="literal">ER_LIMITED_PART_RANGE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The %s handler only supports 32 bit integers in VALUES
    </p></li><li class="listitem"><p><a name="error_er_plugin_is_not_loaded"></a>
      <a class="indexterm" name="idm46734189834112"></a>

      <a class="indexterm" name="idm46734189833072"></a>

      Error number: <code class="literal">1524</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_plugin_is_not_loaded"><code class="literal">ER_PLUGIN_IS_NOT_LOADED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Plugin '%s' is not loaded
    </p></li><li class="listitem"><p><a name="error_er_wrong_value"></a>
      <a class="indexterm" name="idm46734189827088"></a>

      <a class="indexterm" name="idm46734189826032"></a>

      Error number: <code class="literal">1525</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_value"><code class="literal">ER_WRONG_VALUE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Incorrect %s value: '%s'
    </p></li><li class="listitem"><p><a name="error_er_no_partition_for_given_value"></a>
      <a class="indexterm" name="idm46734189820080"></a>

      <a class="indexterm" name="idm46734189818976"></a>

      Error number: <code class="literal">1526</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_partition_for_given_value"><code class="literal">ER_NO_PARTITION_FOR_GIVEN_VALUE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Table has no partition for value %s
    </p></li><li class="listitem"><p><a name="error_er_filegroup_option_only_once"></a>
      <a class="indexterm" name="idm46734189813008"></a>

      <a class="indexterm" name="idm46734189811904"></a>

      Error number: <code class="literal">1527</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_filegroup_option_only_once"><code class="literal">ER_FILEGROUP_OPTION_ONLY_ONCE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: It is not allowed to specify %s more than once
    </p></li><li class="listitem"><p><a name="error_er_create_filegroup_failed"></a>
      <a class="indexterm" name="idm46734189805872"></a>

      <a class="indexterm" name="idm46734189804832"></a>

      Error number: <code class="literal">1528</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_create_filegroup_failed"><code class="literal">ER_CREATE_FILEGROUP_FAILED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Failed to create %s
    </p></li><li class="listitem"><p><a name="error_er_drop_filegroup_failed"></a>
      <a class="indexterm" name="idm46734189798768"></a>

      <a class="indexterm" name="idm46734189797728"></a>

      Error number: <code class="literal">1529</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_drop_filegroup_failed"><code class="literal">ER_DROP_FILEGROUP_FAILED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Failed to drop %s
    </p></li><li class="listitem"><p><a name="error_er_tablespace_auto_extend_error"></a>
      <a class="indexterm" name="idm46734189791744"></a>

      <a class="indexterm" name="idm46734189790640"></a>

      Error number: <code class="literal">1530</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_tablespace_auto_extend_error"><code class="literal">ER_TABLESPACE_AUTO_EXTEND_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The handler doesn't support autoextend of tablespaces
    </p></li><li class="listitem"><p><a name="error_er_wrong_size_number"></a>
      <a class="indexterm" name="idm46734189784528"></a>

      <a class="indexterm" name="idm46734189783488"></a>

      Error number: <code class="literal">1531</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_size_number"><code class="literal">ER_WRONG_SIZE_NUMBER</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: A size parameter was incorrectly specified, either number
      or on the form 10M
    </p></li><li class="listitem"><p><a name="error_er_size_overflow_error"></a>
      <a class="indexterm" name="idm46734189777344"></a>

      <a class="indexterm" name="idm46734189776304"></a>

      Error number: <code class="literal">1532</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_size_overflow_error"><code class="literal">ER_SIZE_OVERFLOW_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The size number was correct but we don't allow the digit
      part to be more than 2 billion
    </p></li><li class="listitem"><p><a name="error_er_alter_filegroup_failed"></a>
      <a class="indexterm" name="idm46734189770144"></a>

      <a class="indexterm" name="idm46734189769104"></a>

      Error number: <code class="literal">1533</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_alter_filegroup_failed"><code class="literal">ER_ALTER_FILEGROUP_FAILED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Failed to alter: %s
    </p></li><li class="listitem"><p><a name="error_er_binlog_row_logging_failed"></a>
      <a class="indexterm" name="idm46734189763104"></a>

      <a class="indexterm" name="idm46734189762064"></a>

      Error number: <code class="literal">1534</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_row_logging_failed"><code class="literal">ER_BINLOG_ROW_LOGGING_FAILED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Writing one row to the row-based binary log failed
    </p></li><li class="listitem"><p><a name="error_er_binlog_row_wrong_table_def"></a>
      <a class="indexterm" name="idm46734189756048"></a>

      <a class="indexterm" name="idm46734189754944"></a>

      Error number: <code class="literal">1535</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_row_wrong_table_def"><code class="literal">ER_BINLOG_ROW_WRONG_TABLE_DEF</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Table definition on master and slave does not match: %s
    </p></li><li class="listitem"><p><a name="error_er_binlog_row_rbr_to_sbr"></a>
      <a class="indexterm" name="idm46734189748960"></a>

      <a class="indexterm" name="idm46734189747920"></a>

      Error number: <code class="literal">1536</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_row_rbr_to_sbr"><code class="literal">ER_BINLOG_ROW_RBR_TO_SBR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Slave running with --log-slave-updates must use row-based
      binary logging to be able to replicate row-based binary log events
    </p></li><li class="listitem"><p><a name="error_er_event_already_exists"></a>
      <a class="indexterm" name="idm46734189741824"></a>

      <a class="indexterm" name="idm46734189740784"></a>

      Error number: <code class="literal">1537</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_already_exists"><code class="literal">ER_EVENT_ALREADY_EXISTS</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Event '%s' already exists
    </p></li><li class="listitem"><p><a name="error_er_event_store_failed"></a>
      <a class="indexterm" name="idm46734189734752"></a>

      <a class="indexterm" name="idm46734189733712"></a>

      Error number: <code class="literal">1538</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_store_failed"><code class="literal">ER_EVENT_STORE_FAILED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Failed to store event %s. Error code %d from storage
      engine.
    </p></li><li class="listitem"><p><a name="error_er_event_does_not_exist"></a>
      <a class="indexterm" name="idm46734189727584"></a>

      <a class="indexterm" name="idm46734189726544"></a>

      Error number: <code class="literal">1539</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_does_not_exist"><code class="literal">ER_EVENT_DOES_NOT_EXIST</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Unknown event '%s'
    </p></li><li class="listitem"><p><a name="error_er_event_cant_alter"></a>
      <a class="indexterm" name="idm46734189720528"></a>

      <a class="indexterm" name="idm46734189719488"></a>

      Error number: <code class="literal">1540</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_cant_alter"><code class="literal">ER_EVENT_CANT_ALTER</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Failed to alter event '%s'
    </p></li><li class="listitem"><p><a name="error_er_event_drop_failed"></a>
      <a class="indexterm" name="idm46734189713456"></a>

      <a class="indexterm" name="idm46734189712416"></a>

      Error number: <code class="literal">1541</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_drop_failed"><code class="literal">ER_EVENT_DROP_FAILED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Failed to drop %s
    </p></li><li class="listitem"><p><a name="error_er_event_interval_not_positive_or_too_big"></a>
      <a class="indexterm" name="idm46734189706416"></a>

      <a class="indexterm" name="idm46734189705376"></a>

      Error number: <code class="literal">1542</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_interval_not_positive_or_too_big"><code class="literal">ER_EVENT_INTERVAL_NOT_POSITIVE_OR_TOO_BIG</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: INTERVAL is either not positive or too big
    </p></li><li class="listitem"><p><a name="error_er_event_ends_before_starts"></a>
      <a class="indexterm" name="idm46734189699296"></a>

      <a class="indexterm" name="idm46734189698256"></a>

      Error number: <code class="literal">1543</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_ends_before_starts"><code class="literal">ER_EVENT_ENDS_BEFORE_STARTS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: ENDS is either invalid or before STARTS
    </p></li><li class="listitem"><p><a name="error_er_event_exec_time_in_the_past"></a>
      <a class="indexterm" name="idm46734189692240"></a>

      <a class="indexterm" name="idm46734189691136"></a>

      Error number: <code class="literal">1544</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_exec_time_in_the_past"><code class="literal">ER_EVENT_EXEC_TIME_IN_THE_PAST</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Event execution time is in the past. Event has been
      disabled
    </p></li><li class="listitem"><p><a name="error_er_event_open_table_failed"></a>
      <a class="indexterm" name="idm46734189685088"></a>

      <a class="indexterm" name="idm46734189684048"></a>

      Error number: <code class="literal">1545</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_open_table_failed"><code class="literal">ER_EVENT_OPEN_TABLE_FAILED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Failed to open mysql.event
    </p></li><li class="listitem"><p><a name="error_er_event_neither_m_expr_nor_m_at"></a>
      <a class="indexterm" name="idm46734189678048"></a>

      <a class="indexterm" name="idm46734189676944"></a>

      Error number: <code class="literal">1546</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_neither_m_expr_nor_m_at"><code class="literal">ER_EVENT_NEITHER_M_EXPR_NOR_M_AT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: No datetime expression provided
    </p></li><li class="listitem"><p><a name="error_er_obsolete_col_count_doesnt_match_corrupted"></a>
      <a class="indexterm" name="idm46734189670880"></a>

      <a class="indexterm" name="idm46734189669840"></a>

      Error number: <code class="literal">1547</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_obsolete_col_count_doesnt_match_corrupted"><code class="literal">ER_OBSOLETE_COL_COUNT_DOESNT_MATCH_CORRUPTED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Column count of mysql.%s is wrong. Expected %d, found %d.
      The table is probably corrupted
    </p></li><li class="listitem"><p><a name="error_er_obsolete_cannot_load_from_table"></a>
      <a class="indexterm" name="idm46734189663664"></a>

      <a class="indexterm" name="idm46734189662624"></a>

      Error number: <code class="literal">1548</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_obsolete_cannot_load_from_table"><code class="literal">ER_OBSOLETE_CANNOT_LOAD_FROM_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot load from mysql.%s. The table is probably
      corrupted
    </p></li><li class="listitem"><p><a name="error_er_event_cannot_delete"></a>
      <a class="indexterm" name="idm46734189656560"></a>

      <a class="indexterm" name="idm46734189655520"></a>

      Error number: <code class="literal">1549</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_cannot_delete"><code class="literal">ER_EVENT_CANNOT_DELETE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Failed to delete the event from mysql.event
    </p></li><li class="listitem"><p><a name="error_er_event_compile_error"></a>
      <a class="indexterm" name="idm46734189649536"></a>

      <a class="indexterm" name="idm46734189648496"></a>

      Error number: <code class="literal">1550</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_compile_error"><code class="literal">ER_EVENT_COMPILE_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Error during compilation of event's body
    </p></li><li class="listitem"><p><a name="error_er_event_same_name"></a>
      <a class="indexterm" name="idm46734189642448"></a>

      <a class="indexterm" name="idm46734189641408"></a>

      Error number: <code class="literal">1551</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_same_name"><code class="literal">ER_EVENT_SAME_NAME</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Same old and new event name
    </p></li><li class="listitem"><p><a name="error_er_event_data_too_long"></a>
      <a class="indexterm" name="idm46734189635376"></a>

      <a class="indexterm" name="idm46734189634336"></a>

      Error number: <code class="literal">1552</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_data_too_long"><code class="literal">ER_EVENT_DATA_TOO_LONG</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Data for column '%s' too long
    </p></li><li class="listitem"><p><a name="error_er_drop_index_fk"></a>
      <a class="indexterm" name="idm46734189628416"></a>

      <a class="indexterm" name="idm46734189627360"></a>

      Error number: <code class="literal">1553</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_drop_index_fk"><code class="literal">ER_DROP_INDEX_FK</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Cannot drop index '%s': needed in a foreign key
      constraint
    </p><p>
      <code class="literal">InnoDB</code> reports this error when you attempt to
      drop the last index that can enforce a particular referential
      constraint.
    </p><p>
      For optimal performance with DML statements,
      <code class="literal">InnoDB</code> requires an index to exist on
      <a class="link" href="glossary.html#glos_foreign_key" title="foreign key">foreign key</a> columns, so
      that <code class="literal">UPDATE</code> and <code class="literal">DELETE</code>
      operations on a <a class="link" href="glossary.html#glos_parent_table" title="parent table">parent
      table</a> can easily check whether corresponding rows exist in
      the <a class="link" href="glossary.html#glos_child_table" title="child table">child table</a>. MySQL
      creates or drops such indexes automatically when needed, as a
      side-effect of <a class="link" href="sql-statements.html#create-table" title="13.1.18 CREATE TABLE Statement"><code class="literal">CREATE TABLE</code></a>,
      <a class="link" href="sql-statements.html#create-index" title="13.1.14 CREATE INDEX Statement"><code class="literal">CREATE INDEX</code></a>, and
      <a class="link" href="sql-statements.html#alter-table" title="13.1.8 ALTER TABLE Statement"><code class="literal">ALTER TABLE</code></a> statements.
    </p><p>
      When you drop an index, <code class="literal">InnoDB</code> checks if the
      index is used for checking a foreign key constraint. It is still
      OK to drop the index if there is another index that can be used to
      enforce the same constraint. <code class="literal">InnoDB</code> prevents
      you from dropping the last index that can enforce a particular
      referential constraint.
    </p></li><li class="listitem"><p><a name="error_er_warn_deprecated_syntax_with_ver"></a>
      <a class="indexterm" name="idm46734189608944"></a>

      <a class="indexterm" name="idm46734189607904"></a>

      Error number: <code class="literal">1554</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_deprecated_syntax_with_ver"><code class="literal">ER_WARN_DEPRECATED_SYNTAX_WITH_VER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The syntax '%s' is deprecated and will be removed in
      MySQL %s. Please use %s instead
    </p></li><li class="listitem"><p><a name="error_er_cant_write_lock_log_table"></a>
      <a class="indexterm" name="idm46734189601744"></a>

      <a class="indexterm" name="idm46734189600704"></a>

      Error number: <code class="literal">1555</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_write_lock_log_table"><code class="literal">ER_CANT_WRITE_LOCK_LOG_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: You can't write-lock a log table. Only read access is
      possible
    </p></li><li class="listitem"><p><a name="error_er_cant_lock_log_table"></a>
      <a class="indexterm" name="idm46734189594656"></a>

      <a class="indexterm" name="idm46734189593616"></a>

      Error number: <code class="literal">1556</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_lock_log_table"><code class="literal">ER_CANT_LOCK_LOG_TABLE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: You can't use locks with log tables.
    </p></li><li class="listitem"><p><a name="error_er_foreign_duplicate_key_old_unused"></a>
      <a class="indexterm" name="idm46734189587520"></a>

      <a class="indexterm" name="idm46734189586480"></a>

      Error number: <code class="literal">1557</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_foreign_duplicate_key_old_unused"><code class="literal">ER_FOREIGN_DUPLICATE_KEY_OLD_UNUSED</code></a>;
      SQLSTATE: <code class="literal">23000</code>
    </p><p>
      Message: Upholding foreign key constraints for table '%s', entry
      '%s', key %d would lead to a duplicate entry
    </p></li><li class="listitem"><p><a name="error_er_col_count_doesnt_match_please_update"></a>
      <a class="indexterm" name="idm46734189580320"></a>

      <a class="indexterm" name="idm46734189579280"></a>

      Error number: <code class="literal">1558</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_col_count_doesnt_match_please_update"><code class="literal">ER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Column count of mysql.%s is wrong. Expected %d, found %d.
      Created with MySQL %d, now running %d. Please use mysql_upgrade to
      fix this error.
    </p></li><li class="listitem"><p><a name="error_er_temp_table_prevents_switch_out_of_rbr"></a>
      <a class="indexterm" name="idm46734189573008"></a>

      <a class="indexterm" name="idm46734189571968"></a>

      Error number: <code class="literal">1559</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_temp_table_prevents_switch_out_of_rbr"><code class="literal">ER_TEMP_TABLE_PREVENTS_SWITCH_OUT_OF_RBR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot switch out of the row-based binary log format when
      the session has open temporary tables
    </p></li><li class="listitem"><p><a name="error_er_stored_function_prevents_switch_binlog_format"></a>
      <a class="indexterm" name="idm46734189565776"></a>

      <a class="indexterm" name="idm46734189564656"></a>

      Error number: <code class="literal">1560</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_stored_function_prevents_switch_binlog_format"><code class="literal">ER_STORED_FUNCTION_PREVENTS_SWITCH_BINLOG_FORMAT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot change the binary logging format inside a stored
      function or trigger
    </p></li><li class="listitem"><p><a name="error_er_ndb_cant_switch_binlog_format"></a>
      <a class="indexterm" name="idm46734189558544"></a>

      <a class="indexterm" name="idm46734189557440"></a>

      Error number: <code class="literal">1561</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_ndb_cant_switch_binlog_format"><code class="literal">ER_NDB_CANT_SWITCH_BINLOG_FORMAT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The NDB cluster engine does not support changing the
      binlog format on the fly yet
    </p></li><li class="listitem"><p><a name="error_er_partition_no_temporary"></a>
      <a class="indexterm" name="idm46734189551296"></a>

      <a class="indexterm" name="idm46734189550256"></a>

      Error number: <code class="literal">1562</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_no_temporary"><code class="literal">ER_PARTITION_NO_TEMPORARY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot create temporary table with partitions
    </p></li><li class="listitem"><p><a name="error_er_partition_const_domain_error"></a>
      <a class="indexterm" name="idm46734189544176"></a>

      <a class="indexterm" name="idm46734189543072"></a>

      Error number: <code class="literal">1563</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_const_domain_error"><code class="literal">ER_PARTITION_CONST_DOMAIN_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Partition constant is out of partition function domain
    </p></li><li class="listitem"><p><a name="error_er_partition_function_is_not_allowed"></a>
      <a class="indexterm" name="idm46734189537040"></a>

      <a class="indexterm" name="idm46734189536000"></a>

      Error number: <code class="literal">1564</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_function_is_not_allowed"><code class="literal">ER_PARTITION_FUNCTION_IS_NOT_ALLOWED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: This partition function is not allowed
    </p></li><li class="listitem"><p><a name="error_er_ddl_log_error"></a>
      <a class="indexterm" name="idm46734189529936"></a>

      <a class="indexterm" name="idm46734189528880"></a>

      Error number: <code class="literal">1565</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_ddl_log_error"><code class="literal">ER_DDL_LOG_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Error in DDL log
    </p></li><li class="listitem"><p><a name="error_er_null_in_values_less_than"></a>
      <a class="indexterm" name="idm46734189522896"></a>

      <a class="indexterm" name="idm46734189521856"></a>

      Error number: <code class="literal">1566</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_null_in_values_less_than"><code class="literal">ER_NULL_IN_VALUES_LESS_THAN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Not allowed to use NULL value in VALUES LESS THAN
    </p></li><li class="listitem"><p><a name="error_er_wrong_partition_name"></a>
      <a class="indexterm" name="idm46734189515776"></a>

      <a class="indexterm" name="idm46734189514736"></a>

      Error number: <code class="literal">1567</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_partition_name"><code class="literal">ER_WRONG_PARTITION_NAME</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Incorrect partition name
    </p></li><li class="listitem"><p><a name="error_er_cant_change_tx_characteristics"></a>
      <a class="indexterm" name="idm46734189508704"></a>

      <a class="indexterm" name="idm46734189507600"></a>

      Error number: <code class="literal">1568</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_change_tx_characteristics"><code class="literal">ER_CANT_CHANGE_TX_CHARACTERISTICS</code></a>;
      SQLSTATE: <code class="literal">25001</code>
    </p><p>
      Message: Transaction characteristics can't be changed while a
      transaction is in progress
    </p></li><li class="listitem"><p><a name="error_er_dup_entry_autoincrement_case"></a>
      <a class="indexterm" name="idm46734189501568"></a>

      <a class="indexterm" name="idm46734189500464"></a>

      Error number: <code class="literal">1569</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_dup_entry_autoincrement_case"><code class="literal">ER_DUP_ENTRY_AUTOINCREMENT_CASE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: ALTER TABLE causes auto_increment resequencing, resulting
      in duplicate entry '%s' for key '%s'
    </p></li><li class="listitem"><p><a name="error_er_event_modify_queue_error"></a>
      <a class="indexterm" name="idm46734189494368"></a>

      <a class="indexterm" name="idm46734189493328"></a>

      Error number: <code class="literal">1570</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_modify_queue_error"><code class="literal">ER_EVENT_MODIFY_QUEUE_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Internal scheduler error %d
    </p></li><li class="listitem"><p><a name="error_er_event_set_var_error"></a>
      <a class="indexterm" name="idm46734189487328"></a>

      <a class="indexterm" name="idm46734189486288"></a>

      Error number: <code class="literal">1571</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_set_var_error"><code class="literal">ER_EVENT_SET_VAR_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Error during starting/stopping of the scheduler. Error
      code %u
    </p></li><li class="listitem"><p><a name="error_er_partition_merge_error"></a>
      <a class="indexterm" name="idm46734189480144"></a>

      <a class="indexterm" name="idm46734189479104"></a>

      Error number: <code class="literal">1572</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_merge_error"><code class="literal">ER_PARTITION_MERGE_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Engine cannot be used in partitioned tables
    </p></li><li class="listitem"><p><a name="error_er_cant_activate_log"></a>
      <a class="indexterm" name="idm46734189473088"></a>

      <a class="indexterm" name="idm46734189472048"></a>

      Error number: <code class="literal">1573</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_activate_log"><code class="literal">ER_CANT_ACTIVATE_LOG</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Cannot activate '%s' log
    </p></li><li class="listitem"><p><a name="error_er_rbr_not_available"></a>
      <a class="indexterm" name="idm46734189466016"></a>

      <a class="indexterm" name="idm46734189464976"></a>

      Error number: <code class="literal">1574</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_rbr_not_available"><code class="literal">ER_RBR_NOT_AVAILABLE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The server was not built with row-based replication
    </p></li><li class="listitem"><p><a name="error_er_base64_decode_error"></a>
      <a class="indexterm" name="idm46734189458976"></a>

      <a class="indexterm" name="idm46734189457936"></a>

      Error number: <code class="literal">1575</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_base64_decode_error"><code class="literal">ER_BASE64_DECODE_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Decoding of base64 string failed
    </p></li><li class="listitem"><p><a name="error_er_event_recursion_forbidden"></a>
      <a class="indexterm" name="idm46734189451840"></a>

      <a class="indexterm" name="idm46734189450800"></a>

      Error number: <code class="literal">1576</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_recursion_forbidden"><code class="literal">ER_EVENT_RECURSION_FORBIDDEN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Recursion of EVENT DDL statements is forbidden when body
      is present
    </p></li><li class="listitem"><p><a name="error_er_events_db_error"></a>
      <a class="indexterm" name="idm46734189444752"></a>

      <a class="indexterm" name="idm46734189443712"></a>

      Error number: <code class="literal">1577</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_events_db_error"><code class="literal">ER_EVENTS_DB_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Cannot proceed because system tables used by Event
      Scheduler were found damaged at server start
    </p><p>
      To address this issue, try running
      <a class="link" href="programs.html#mysql-upgrade" title="4.4.7 mysql_upgrade — Check and Upgrade MySQL Tables"><span class="command"><strong>mysql_upgrade</strong></span></a>.
    </p></li><li class="listitem"><p><a name="error_er_only_integers_allowed"></a>
      <a class="indexterm" name="idm46734189435920"></a>

      <a class="indexterm" name="idm46734189434880"></a>

      Error number: <code class="literal">1578</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_only_integers_allowed"><code class="literal">ER_ONLY_INTEGERS_ALLOWED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Only integers allowed as number here
    </p></li><li class="listitem"><p><a name="error_er_unsuported_log_engine"></a>
      <a class="indexterm" name="idm46734189428800"></a>

      <a class="indexterm" name="idm46734189427760"></a>

      Error number: <code class="literal">1579</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unsuported_log_engine"><code class="literal">ER_UNSUPORTED_LOG_ENGINE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: This storage engine cannot be used for log tables"
    </p></li><li class="listitem"><p><a name="error_er_bad_log_statement"></a>
      <a class="indexterm" name="idm46734189421680"></a>

      <a class="indexterm" name="idm46734189420640"></a>

      Error number: <code class="literal">1580</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_bad_log_statement"><code class="literal">ER_BAD_LOG_STATEMENT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: You cannot '%s' a log table if logging is enabled
    </p></li><li class="listitem"><p><a name="error_er_cant_rename_log_table"></a>
      <a class="indexterm" name="idm46734189414592"></a>

      <a class="indexterm" name="idm46734189413552"></a>

      Error number: <code class="literal">1581</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_rename_log_table"><code class="literal">ER_CANT_RENAME_LOG_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot rename '%s'. When logging enabled, rename to/from
      log table must rename two tables: the log table to an archive
      table and another table back to '%s'
    </p></li><li class="listitem"><p><a name="error_er_wrong_paramcount_to_native_fct"></a>
      <a class="indexterm" name="idm46734189407408"></a>

      <a class="indexterm" name="idm46734189406304"></a>

      Error number: <code class="literal">1582</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_paramcount_to_native_fct"><code class="literal">ER_WRONG_PARAMCOUNT_TO_NATIVE_FCT</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Incorrect parameter count in the call to native function
      '%s'
    </p></li><li class="listitem"><p><a name="error_er_wrong_parameters_to_native_fct"></a>
      <a class="indexterm" name="idm46734189400240"></a>

      <a class="indexterm" name="idm46734189399136"></a>

      Error number: <code class="literal">1583</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_parameters_to_native_fct"><code class="literal">ER_WRONG_PARAMETERS_TO_NATIVE_FCT</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Incorrect parameters in the call to native function '%s'
    </p></li><li class="listitem"><p><a name="error_er_wrong_parameters_to_stored_fct"></a>
      <a class="indexterm" name="idm46734189393072"></a>

      <a class="indexterm" name="idm46734189391968"></a>

      Error number: <code class="literal">1584</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_parameters_to_stored_fct"><code class="literal">ER_WRONG_PARAMETERS_TO_STORED_FCT</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Incorrect parameters in the call to stored function %s
    </p></li><li class="listitem"><p><a name="error_er_native_fct_name_collision"></a>
      <a class="indexterm" name="idm46734189385984"></a>

      <a class="indexterm" name="idm46734189384944"></a>

      Error number: <code class="literal">1585</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_native_fct_name_collision"><code class="literal">ER_NATIVE_FCT_NAME_COLLISION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: This function '%s' has the same name as a native function
    </p></li><li class="listitem"><p><a name="error_er_dup_entry_with_key_name"></a>
      <a class="indexterm" name="idm46734189378896"></a>

      <a class="indexterm" name="idm46734189377856"></a>

      Error number: <code class="literal">1586</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_dup_entry_with_key_name"><code class="literal">ER_DUP_ENTRY_WITH_KEY_NAME</code></a>;
      SQLSTATE: <code class="literal">23000</code>
    </p><p>
      Message: Duplicate entry '%s' for key '%s'
    </p><p>
      The format string for this error is also used with
      <a class="link" href="error-handling.html#error_er_dup_entry"><code class="literal">ER_DUP_ENTRY</code></a>.
    </p></li><li class="listitem"><p><a name="error_er_binlog_purge_emfile"></a>
      <a class="indexterm" name="idm46734189370224"></a>

      <a class="indexterm" name="idm46734189369184"></a>

      Error number: <code class="literal">1587</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_purge_emfile"><code class="literal">ER_BINLOG_PURGE_EMFILE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Too many files opened, please execute the command again
    </p></li><li class="listitem"><p><a name="error_er_event_cannot_create_in_the_past"></a>
      <a class="indexterm" name="idm46734189363136"></a>

      <a class="indexterm" name="idm46734189362096"></a>

      Error number: <code class="literal">1588</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_cannot_create_in_the_past"><code class="literal">ER_EVENT_CANNOT_CREATE_IN_THE_PAST</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Event execution time is in the past and ON COMPLETION NOT
      PRESERVE is set. The event was dropped immediately after creation.
    </p></li><li class="listitem"><p><a name="error_er_event_cannot_alter_in_the_past"></a>
      <a class="indexterm" name="idm46734189355904"></a>

      <a class="indexterm" name="idm46734189354800"></a>

      Error number: <code class="literal">1589</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_cannot_alter_in_the_past"><code class="literal">ER_EVENT_CANNOT_ALTER_IN_THE_PAST</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Event execution time is in the past and ON COMPLETION NOT
      PRESERVE is set. The event was not changed. Specify a time in the
      future.
    </p></li><li class="listitem"><p><a name="error_er_slave_incident"></a>
      <a class="indexterm" name="idm46734189348720"></a>

      <a class="indexterm" name="idm46734189347664"></a>

      Error number: <code class="literal">1590</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_incident"><code class="literal">ER_SLAVE_INCIDENT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The incident %s occured on the master. Message: %s
    </p></li><li class="listitem"><p><a name="error_er_no_partition_for_given_value_silent"></a>
      <a class="indexterm" name="idm46734189341648"></a>

      <a class="indexterm" name="idm46734189340608"></a>

      Error number: <code class="literal">1591</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_partition_for_given_value_silent"><code class="literal">ER_NO_PARTITION_FOR_GIVEN_VALUE_SILENT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Table has no partition for some existing values
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_statement"></a>
      <a class="indexterm" name="idm46734189334672"></a>

      <a class="indexterm" name="idm46734189333632"></a>

      Error number: <code class="literal">1592</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_statement"><code class="literal">ER_BINLOG_UNSAFE_STATEMENT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Unsafe statement written to the binary log using
      statement format since BINLOG_FORMAT = STATEMENT. %s
    </p></li><li class="listitem"><p><a name="error_er_slave_fatal_error"></a>
      <a class="indexterm" name="idm46734189327552"></a>

      <a class="indexterm" name="idm46734189326512"></a>

      Error number: <code class="literal">1593</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_fatal_error"><code class="literal">ER_SLAVE_FATAL_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Fatal error: %s
    </p></li><li class="listitem"><p><a name="error_er_slave_relay_log_read_failure"></a>
      <a class="indexterm" name="idm46734189320560"></a>

      <a class="indexterm" name="idm46734189319456"></a>

      Error number: <code class="literal">1594</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_relay_log_read_failure"><code class="literal">ER_SLAVE_RELAY_LOG_READ_FAILURE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Relay log read failure: %s
    </p></li><li class="listitem"><p><a name="error_er_slave_relay_log_write_failure"></a>
      <a class="indexterm" name="idm46734189313440"></a>

      <a class="indexterm" name="idm46734189312336"></a>

      Error number: <code class="literal">1595</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_relay_log_write_failure"><code class="literal">ER_SLAVE_RELAY_LOG_WRITE_FAILURE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Relay log write failure: %s
    </p></li><li class="listitem"><p><a name="error_er_slave_create_event_failure"></a>
      <a class="indexterm" name="idm46734189306320"></a>

      <a class="indexterm" name="idm46734189305216"></a>

      Error number: <code class="literal">1596</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_create_event_failure"><code class="literal">ER_SLAVE_CREATE_EVENT_FAILURE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Failed to create %s
    </p></li><li class="listitem"><p><a name="error_er_slave_master_com_failure"></a>
      <a class="indexterm" name="idm46734189299200"></a>

      <a class="indexterm" name="idm46734189298160"></a>

      Error number: <code class="literal">1597</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_master_com_failure"><code class="literal">ER_SLAVE_MASTER_COM_FAILURE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Master command %s failed: %s
    </p></li><li class="listitem"><p><a name="error_er_binlog_logging_impossible"></a>
      <a class="indexterm" name="idm46734189292160"></a>

      <a class="indexterm" name="idm46734189291120"></a>

      Error number: <code class="literal">1598</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_logging_impossible"><code class="literal">ER_BINLOG_LOGGING_IMPOSSIBLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Binary logging not possible. Message: %s
    </p></li><li class="listitem"><p><a name="error_er_view_no_creation_ctx"></a>
      <a class="indexterm" name="idm46734189285040"></a>

      <a class="indexterm" name="idm46734189284000"></a>

      Error number: <code class="literal">1599</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_no_creation_ctx"><code class="literal">ER_VIEW_NO_CREATION_CTX</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: View `%s`.`%s` has no creation context
    </p></li><li class="listitem"><p><a name="error_er_view_invalid_creation_ctx"></a>
      <a class="indexterm" name="idm46734189277952"></a>

      <a class="indexterm" name="idm46734189276912"></a>

      Error number: <code class="literal">1600</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_view_invalid_creation_ctx"><code class="literal">ER_VIEW_INVALID_CREATION_CTX</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Creation context of view `%s`.`%s' is invalid
    </p></li><li class="listitem"><p><a name="error_er_sr_invalid_creation_ctx"></a>
      <a class="indexterm" name="idm46734189270896"></a>

      <a class="indexterm" name="idm46734189269856"></a>

      Error number: <code class="literal">1601</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sr_invalid_creation_ctx"><code class="literal">ER_SR_INVALID_CREATION_CTX</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Creation context of stored routine `%s`.`%s` is invalid
    </p></li><li class="listitem"><p><a name="error_er_trg_corrupted_file"></a>
      <a class="indexterm" name="idm46734189263824"></a>

      <a class="indexterm" name="idm46734189262784"></a>

      Error number: <code class="literal">1602</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_trg_corrupted_file"><code class="literal">ER_TRG_CORRUPTED_FILE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Corrupted TRG file for table `%s`.`%s`
    </p></li><li class="listitem"><p><a name="error_er_trg_no_creation_ctx"></a>
      <a class="indexterm" name="idm46734189256736"></a>

      <a class="indexterm" name="idm46734189255696"></a>

      Error number: <code class="literal">1603</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_trg_no_creation_ctx"><code class="literal">ER_TRG_NO_CREATION_CTX</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Triggers for table `%s`.`%s` have no creation context
    </p></li><li class="listitem"><p><a name="error_er_trg_invalid_creation_ctx"></a>
      <a class="indexterm" name="idm46734189249632"></a>

      <a class="indexterm" name="idm46734189248592"></a>

      Error number: <code class="literal">1604</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_trg_invalid_creation_ctx"><code class="literal">ER_TRG_INVALID_CREATION_CTX</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Trigger creation context of table `%s`.`%s` is invalid
    </p></li><li class="listitem"><p><a name="error_er_event_invalid_creation_ctx"></a>
      <a class="indexterm" name="idm46734189242560"></a>

      <a class="indexterm" name="idm46734189241456"></a>

      Error number: <code class="literal">1605</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_event_invalid_creation_ctx"><code class="literal">ER_EVENT_INVALID_CREATION_CTX</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Creation context of event `%s`.`%s` is invalid
    </p></li><li class="listitem"><p><a name="error_er_trg_cant_open_table"></a>
      <a class="indexterm" name="idm46734189235472"></a>

      <a class="indexterm" name="idm46734189234432"></a>

      Error number: <code class="literal">1606</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_trg_cant_open_table"><code class="literal">ER_TRG_CANT_OPEN_TABLE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Cannot open table for trigger `%s`.`%s`
    </p></li><li class="listitem"><p><a name="error_er_cant_create_sroutine"></a>
      <a class="indexterm" name="idm46734189228448"></a>

      <a class="indexterm" name="idm46734189227408"></a>

      Error number: <code class="literal">1607</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_create_sroutine"><code class="literal">ER_CANT_CREATE_SROUTINE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Cannot create stored routine `%s`. Check warnings
    </p></li><li class="listitem"><p><a name="error_er_never_used"></a>
      <a class="indexterm" name="idm46734189221408"></a>

      <a class="indexterm" name="idm46734189220352"></a>

      Error number: <code class="literal">1608</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_never_used"><code class="literal">ER_NEVER_USED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Ambiguous slave modes combination. %s
    </p></li><li class="listitem"><p><a name="error_er_no_format_description_event_before_binlog_statement"></a>
      <a class="indexterm" name="idm46734189214240"></a>

      <a class="indexterm" name="idm46734189213200"></a>

      Error number: <code class="literal">1609</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_format_description_event_before_binlog_statement"><code class="literal">ER_NO_FORMAT_DESCRIPTION_EVENT_BEFORE_BINLOG_STATEMENT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The BINLOG statement of type `%s` was not preceded by a
      format description BINLOG statement.
    </p></li><li class="listitem"><p><a name="error_er_slave_corrupt_event"></a>
      <a class="indexterm" name="idm46734189206896"></a>

      <a class="indexterm" name="idm46734189205856"></a>

      Error number: <code class="literal">1610</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_corrupt_event"><code class="literal">ER_SLAVE_CORRUPT_EVENT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Corrupted replication event was detected
    </p></li><li class="listitem"><p><a name="error_er_load_data_invalid_column"></a>
      <a class="indexterm" name="idm46734189199824"></a>

      <a class="indexterm" name="idm46734189198784"></a>

      Error number: <code class="literal">1611</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_load_data_invalid_column"><code class="literal">ER_LOAD_DATA_INVALID_COLUMN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Invalid column reference (%s) in LOAD DATA
    </p><p>
      <a class="link" href="error-handling.html#error_er_load_data_invalid_column"><code class="literal">ER_LOAD_DATA_INVALID_COLUMN</code></a> was
      removed after 5.7.7.
    </p></li><li class="listitem"><p><a name="error_er_load_data_invalid_column_unused"></a>
      <a class="indexterm" name="idm46734189191040"></a>

      <a class="indexterm" name="idm46734189190000"></a>

      Error number: <code class="literal">1611</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_load_data_invalid_column_unused"><code class="literal">ER_LOAD_DATA_INVALID_COLUMN_UNUSED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Invalid column reference (%s) in LOAD DATA
    </p><p>
      <a class="link" href="error-handling.html#error_er_load_data_invalid_column_unused"><code class="literal">ER_LOAD_DATA_INVALID_COLUMN_UNUSED</code></a>
      was added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_log_purge_no_file"></a>
      <a class="indexterm" name="idm46734189182176"></a>

      <a class="indexterm" name="idm46734189181136"></a>

      Error number: <code class="literal">1612</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_log_purge_no_file"><code class="literal">ER_LOG_PURGE_NO_FILE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Being purged log %s was not found
    </p></li><li class="listitem"><p><a name="error_er_xa_rbtimeout"></a>
      <a class="indexterm" name="idm46734189175216"></a>

      <a class="indexterm" name="idm46734189174160"></a>

      Error number: <code class="literal">1613</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_xa_rbtimeout"><code class="literal">ER_XA_RBTIMEOUT</code></a>; SQLSTATE:
      <code class="literal">XA106</code>
    </p><p>
      Message: XA_RBTIMEOUT: Transaction branch was rolled back: took
      too long
    </p></li><li class="listitem"><p><a name="error_er_xa_rbdeadlock"></a>
      <a class="indexterm" name="idm46734189168160"></a>

      <a class="indexterm" name="idm46734189167104"></a>

      Error number: <code class="literal">1614</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_xa_rbdeadlock"><code class="literal">ER_XA_RBDEADLOCK</code></a>; SQLSTATE:
      <code class="literal">XA102</code>
    </p><p>
      Message: XA_RBDEADLOCK: Transaction branch was rolled back:
      deadlock was detected
    </p></li><li class="listitem"><p><a name="error_er_need_reprepare"></a>
      <a class="indexterm" name="idm46734189161168"></a>

      <a class="indexterm" name="idm46734189160112"></a>

      Error number: <code class="literal">1615</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_need_reprepare"><code class="literal">ER_NEED_REPREPARE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Prepared statement needs to be re-prepared
    </p></li><li class="listitem"><p><a name="error_er_delayed_not_supported"></a>
      <a class="indexterm" name="idm46734189154096"></a>

      <a class="indexterm" name="idm46734189153056"></a>

      Error number: <code class="literal">1616</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_delayed_not_supported"><code class="literal">ER_DELAYED_NOT_SUPPORTED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: DELAYED option not supported for table '%s'
    </p></li><li class="listitem"><p><a name="error_warn_no_master_info"></a>
      <a class="indexterm" name="idm46734189146976"></a>

      <a class="indexterm" name="idm46734189145936"></a>

      Error number: <code class="literal">1617</code>; Symbol:
      <a class="link" href="error-handling.html#error_warn_no_master_info"><code class="literal">WARN_NO_MASTER_INFO</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The master info structure does not exist
    </p></li><li class="listitem"><p><a name="error_warn_option_ignored"></a>
      <a class="indexterm" name="idm46734189139952"></a>

      <a class="indexterm" name="idm46734189138912"></a>

      Error number: <code class="literal">1618</code>; Symbol:
      <a class="link" href="error-handling.html#error_warn_option_ignored"><code class="literal">WARN_OPTION_IGNORED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: &lt;%s&gt; option ignored
    </p></li><li class="listitem"><p><a name="error_warn_plugin_delete_builtin"></a>
      <a class="indexterm" name="idm46734189132752"></a>

      <a class="indexterm" name="idm46734189131712"></a>

      Error number: <code class="literal">1619</code>; Symbol:
      <a class="link" href="error-handling.html#error_warn_plugin_delete_builtin"><code class="literal">WARN_PLUGIN_DELETE_BUILTIN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Built-in plugins cannot be deleted
    </p><p>
      <a class="link" href="error-handling.html#error_warn_plugin_delete_builtin"><code class="literal">WARN_PLUGIN_DELETE_BUILTIN</code></a> was
      removed after 5.7.4.
    </p></li><li class="listitem"><p><a name="error_er_plugin_delete_builtin"></a>
      <a class="indexterm" name="idm46734189123968"></a>

      <a class="indexterm" name="idm46734189122928"></a>

      Error number: <code class="literal">1619</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_plugin_delete_builtin"><code class="literal">ER_PLUGIN_DELETE_BUILTIN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Built-in plugins cannot be deleted
    </p><p>
      <a class="link" href="error-handling.html#error_er_plugin_delete_builtin"><code class="literal">ER_PLUGIN_DELETE_BUILTIN</code></a> was added
      in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_warn_plugin_busy"></a>
      <a class="indexterm" name="idm46734189115296"></a>

      <a class="indexterm" name="idm46734189114240"></a>

      Error number: <code class="literal">1620</code>; Symbol:
      <a class="link" href="error-handling.html#error_warn_plugin_busy"><code class="literal">WARN_PLUGIN_BUSY</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Plugin is busy and will be uninstalled on shutdown
    </p></li><li class="listitem"><p><a name="error_er_variable_is_readonly"></a>
      <a class="indexterm" name="idm46734189108288"></a>

      <a class="indexterm" name="idm46734189107248"></a>

      Error number: <code class="literal">1621</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_variable_is_readonly"><code class="literal">ER_VARIABLE_IS_READONLY</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: %s variable '%s' is read-only. Use SET %s to assign the
      value
    </p></li><li class="listitem"><p><a name="error_er_warn_engine_transaction_rollback"></a>
      <a class="indexterm" name="idm46734189101120"></a>

      <a class="indexterm" name="idm46734189100080"></a>

      Error number: <code class="literal">1622</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_engine_transaction_rollback"><code class="literal">ER_WARN_ENGINE_TRANSACTION_ROLLBACK</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Storage engine %s does not support rollback for this
      statement. Transaction rolled back and must be restarted
    </p></li><li class="listitem"><p><a name="error_er_slave_heartbeat_failure"></a>
      <a class="indexterm" name="idm46734189093952"></a>

      <a class="indexterm" name="idm46734189092912"></a>

      Error number: <code class="literal">1623</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_heartbeat_failure"><code class="literal">ER_SLAVE_HEARTBEAT_FAILURE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Unexpected master's heartbeat data: %s
    </p></li><li class="listitem"><p><a name="error_er_slave_heartbeat_value_out_of_range"></a>
      <a class="indexterm" name="idm46734189086848"></a>

      <a class="indexterm" name="idm46734189085808"></a>

      Error number: <code class="literal">1624</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_heartbeat_value_out_of_range"><code class="literal">ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The requested value for the heartbeat period is either
      negative or exceeds the maximum allowed (%s seconds).
    </p></li><li class="listitem"><p><a name="error_er_ndb_replication_schema_error"></a>
      <a class="indexterm" name="idm46734189079680"></a>

      <a class="indexterm" name="idm46734189078576"></a>

      Error number: <code class="literal">1625</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_ndb_replication_schema_error"><code class="literal">ER_NDB_REPLICATION_SCHEMA_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Bad schema for mysql.ndb_replication table. Message: %s
    </p></li><li class="listitem"><p><a name="error_er_conflict_fn_parse_error"></a>
      <a class="indexterm" name="idm46734189072592"></a>

      <a class="indexterm" name="idm46734189071552"></a>

      Error number: <code class="literal">1626</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_conflict_fn_parse_error"><code class="literal">ER_CONFLICT_FN_PARSE_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Error in parsing conflict function. Message: %s
    </p></li><li class="listitem"><p><a name="error_er_exceptions_write_error"></a>
      <a class="indexterm" name="idm46734189065536"></a>

      <a class="indexterm" name="idm46734189064496"></a>

      Error number: <code class="literal">1627</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_exceptions_write_error"><code class="literal">ER_EXCEPTIONS_WRITE_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Write to exceptions table failed. Message: %s"
    </p></li><li class="listitem"><p><a name="error_er_too_long_table_comment"></a>
      <a class="indexterm" name="idm46734189058352"></a>

      <a class="indexterm" name="idm46734189057312"></a>

      Error number: <code class="literal">1628</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_long_table_comment"><code class="literal">ER_TOO_LONG_TABLE_COMMENT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Comment for table '%s' is too long (max = %lu)
    </p></li><li class="listitem"><p><a name="error_er_too_long_field_comment"></a>
      <a class="indexterm" name="idm46734189051168"></a>

      <a class="indexterm" name="idm46734189050128"></a>

      Error number: <code class="literal">1629</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_long_field_comment"><code class="literal">ER_TOO_LONG_FIELD_COMMENT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Comment for field '%s' is too long (max = %lu)
    </p></li><li class="listitem"><p><a name="error_er_func_inexistent_name_collision"></a>
      <a class="indexterm" name="idm46734189044112"></a>

      <a class="indexterm" name="idm46734189043008"></a>

      Error number: <code class="literal">1630</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_func_inexistent_name_collision"><code class="literal">ER_FUNC_INEXISTENT_NAME_COLLISION</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: FUNCTION %s does not exist. Check the 'Function Name
      Parsing and Resolution' section in the Reference Manual
    </p></li><li class="listitem"><p><a name="error_er_database_name"></a>
      <a class="indexterm" name="idm46734189037024"></a>

      <a class="indexterm" name="idm46734189035968"></a>

      Error number: <code class="literal">1631</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_database_name"><code class="literal">ER_DATABASE_NAME</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Database
    </p></li><li class="listitem"><p><a name="error_er_table_name"></a>
      <a class="indexterm" name="idm46734189030096"></a>

      <a class="indexterm" name="idm46734189029040"></a>

      Error number: <code class="literal">1632</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_name"><code class="literal">ER_TABLE_NAME</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Table
    </p></li><li class="listitem"><p><a name="error_er_partition_name"></a>
      <a class="indexterm" name="idm46734189023168"></a>

      <a class="indexterm" name="idm46734189022112"></a>

      Error number: <code class="literal">1633</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_name"><code class="literal">ER_PARTITION_NAME</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Partition
    </p></li><li class="listitem"><p><a name="error_er_subpartition_name"></a>
      <a class="indexterm" name="idm46734189016192"></a>

      <a class="indexterm" name="idm46734189015152"></a>

      Error number: <code class="literal">1634</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_subpartition_name"><code class="literal">ER_SUBPARTITION_NAME</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Subpartition
    </p></li><li class="listitem"><p><a name="error_er_temporary_name"></a>
      <a class="indexterm" name="idm46734189009184"></a>

      <a class="indexterm" name="idm46734189008128"></a>

      Error number: <code class="literal">1635</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_temporary_name"><code class="literal">ER_TEMPORARY_NAME</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Temporary
    </p></li><li class="listitem"><p><a name="error_er_renamed_name"></a>
      <a class="indexterm" name="idm46734189002128"></a>

      <a class="indexterm" name="idm46734189001072"></a>

      Error number: <code class="literal">1636</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_renamed_name"><code class="literal">ER_RENAMED_NAME</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Renamed
    </p></li><li class="listitem"><p><a name="error_er_too_many_concurrent_trxs"></a>
      <a class="indexterm" name="idm46734188995088"></a>

      <a class="indexterm" name="idm46734188994048"></a>

      Error number: <code class="literal">1637</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_many_concurrent_trxs"><code class="literal">ER_TOO_MANY_CONCURRENT_TRXS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Too many active concurrent transactions
    </p></li><li class="listitem"><p><a name="error_warn_non_ascii_separator_not_implemented"></a>
      <a class="indexterm" name="idm46734188987984"></a>

      <a class="indexterm" name="idm46734188986944"></a>

      Error number: <code class="literal">1638</code>; Symbol:
      <a class="link" href="error-handling.html#error_warn_non_ascii_separator_not_implemented"><code class="literal">WARN_NON_ASCII_SEPARATOR_NOT_IMPLEMENTED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Non-ASCII separator arguments are not fully supported
    </p></li><li class="listitem"><p><a name="error_er_debug_sync_timeout"></a>
      <a class="indexterm" name="idm46734188980848"></a>

      <a class="indexterm" name="idm46734188979808"></a>

      Error number: <code class="literal">1639</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_debug_sync_timeout"><code class="literal">ER_DEBUG_SYNC_TIMEOUT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: debug sync point wait timed out
    </p></li><li class="listitem"><p><a name="error_er_debug_sync_hit_limit"></a>
      <a class="indexterm" name="idm46734188973776"></a>

      <a class="indexterm" name="idm46734188972736"></a>

      Error number: <code class="literal">1640</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_debug_sync_hit_limit"><code class="literal">ER_DEBUG_SYNC_HIT_LIMIT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: debug sync point hit limit reached
    </p></li><li class="listitem"><p><a name="error_er_dup_signal_set"></a>
      <a class="indexterm" name="idm46734188966752"></a>

      <a class="indexterm" name="idm46734188965696"></a>

      Error number: <code class="literal">1641</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_dup_signal_set"><code class="literal">ER_DUP_SIGNAL_SET</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Duplicate condition information item '%s'
    </p></li><li class="listitem"><p><a name="error_er_signal_warn"></a>
      <a class="indexterm" name="idm46734188959840"></a>

      <a class="indexterm" name="idm46734188958784"></a>

      Error number: <code class="literal">1642</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_signal_warn"><code class="literal">ER_SIGNAL_WARN</code></a>; SQLSTATE:
      <code class="literal">01000</code>
    </p><p>
      Message: Unhandled user-defined warning condition
    </p></li><li class="listitem"><p><a name="error_er_signal_not_found"></a>
      <a class="indexterm" name="idm46734188952880"></a>

      <a class="indexterm" name="idm46734188951840"></a>

      Error number: <code class="literal">1643</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_signal_not_found"><code class="literal">ER_SIGNAL_NOT_FOUND</code></a>; SQLSTATE:
      <code class="literal">02000</code>
    </p><p>
      Message: Unhandled user-defined not found condition
    </p></li><li class="listitem"><p><a name="error_er_signal_exception"></a>
      <a class="indexterm" name="idm46734188945904"></a>

      <a class="indexterm" name="idm46734188944864"></a>

      Error number: <code class="literal">1644</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_signal_exception"><code class="literal">ER_SIGNAL_EXCEPTION</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Unhandled user-defined exception condition
    </p></li><li class="listitem"><p><a name="error_er_resignal_without_active_handler"></a>
      <a class="indexterm" name="idm46734188938832"></a>

      <a class="indexterm" name="idm46734188937792"></a>

      Error number: <code class="literal">1645</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_resignal_without_active_handler"><code class="literal">ER_RESIGNAL_WITHOUT_ACTIVE_HANDLER</code></a>;
      SQLSTATE: <code class="literal">0K000</code>
    </p><p>
      Message: RESIGNAL when handler not active
    </p></li><li class="listitem"><p><a name="error_er_signal_bad_condition_type"></a>
      <a class="indexterm" name="idm46734188931696"></a>

      <a class="indexterm" name="idm46734188930656"></a>

      Error number: <code class="literal">1646</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_signal_bad_condition_type"><code class="literal">ER_SIGNAL_BAD_CONDITION_TYPE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: SIGNAL/RESIGNAL can only use a CONDITION defined with
      SQLSTATE
    </p></li><li class="listitem"><p><a name="error_warn_cond_item_truncated"></a>
      <a class="indexterm" name="idm46734188924608"></a>

      <a class="indexterm" name="idm46734188923568"></a>

      Error number: <code class="literal">1647</code>; Symbol:
      <a class="link" href="error-handling.html#error_warn_cond_item_truncated"><code class="literal">WARN_COND_ITEM_TRUNCATED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Data truncated for condition item '%s'
    </p></li><li class="listitem"><p><a name="error_er_cond_item_too_long"></a>
      <a class="indexterm" name="idm46734188917488"></a>

      <a class="indexterm" name="idm46734188916448"></a>

      Error number: <code class="literal">1648</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cond_item_too_long"><code class="literal">ER_COND_ITEM_TOO_LONG</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Data too long for condition item '%s'
    </p></li><li class="listitem"><p><a name="error_er_unknown_locale"></a>
      <a class="indexterm" name="idm46734188910512"></a>

      <a class="indexterm" name="idm46734188909456"></a>

      Error number: <code class="literal">1649</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unknown_locale"><code class="literal">ER_UNKNOWN_LOCALE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Unknown locale: '%s'
    </p></li><li class="listitem"><p><a name="error_er_slave_ignore_server_ids"></a>
      <a class="indexterm" name="idm46734188903456"></a>

      <a class="indexterm" name="idm46734188902416"></a>

      Error number: <code class="literal">1650</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_ignore_server_ids"><code class="literal">ER_SLAVE_IGNORE_SERVER_IDS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The requested server id %d clashes with the slave startup
      option --replicate-same-server-id
    </p></li><li class="listitem"><p><a name="error_er_query_cache_disabled"></a>
      <a class="indexterm" name="idm46734188896352"></a>

      <a class="indexterm" name="idm46734188895312"></a>

      Error number: <code class="literal">1651</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_query_cache_disabled"><code class="literal">ER_QUERY_CACHE_DISABLED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Query cache is disabled; restart the server with
      query_cache_type=1 to enable it
    </p></li><li class="listitem"><p><a name="error_er_same_name_partition_field"></a>
      <a class="indexterm" name="idm46734188889280"></a>

      <a class="indexterm" name="idm46734188888240"></a>

      Error number: <code class="literal">1652</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_same_name_partition_field"><code class="literal">ER_SAME_NAME_PARTITION_FIELD</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Duplicate partition field name '%s'
    </p></li><li class="listitem"><p><a name="error_er_partition_column_list_error"></a>
      <a class="indexterm" name="idm46734188882160"></a>

      <a class="indexterm" name="idm46734188881056"></a>

      Error number: <code class="literal">1653</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_column_list_error"><code class="literal">ER_PARTITION_COLUMN_LIST_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Inconsistency in usage of column lists for partitioning
    </p></li><li class="listitem"><p><a name="error_er_wrong_type_column_value_error"></a>
      <a class="indexterm" name="idm46734188875008"></a>

      <a class="indexterm" name="idm46734188873904"></a>

      Error number: <code class="literal">1654</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_type_column_value_error"><code class="literal">ER_WRONG_TYPE_COLUMN_VALUE_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Partition column values of incorrect type
    </p></li><li class="listitem"><p><a name="error_er_too_many_partition_func_fields_error"></a>
      <a class="indexterm" name="idm46734188867824"></a>

      <a class="indexterm" name="idm46734188866784"></a>

      Error number: <code class="literal">1655</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_many_partition_func_fields_error"><code class="literal">ER_TOO_MANY_PARTITION_FUNC_FIELDS_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Too many fields in '%s'
    </p></li><li class="listitem"><p><a name="error_er_maxvalue_in_values_in"></a>
      <a class="indexterm" name="idm46734188860688"></a>

      <a class="indexterm" name="idm46734188859648"></a>

      Error number: <code class="literal">1656</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_maxvalue_in_values_in"><code class="literal">ER_MAXVALUE_IN_VALUES_IN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot use MAXVALUE as value in VALUES IN
    </p></li><li class="listitem"><p><a name="error_er_too_many_values_error"></a>
      <a class="indexterm" name="idm46734188853568"></a>

      <a class="indexterm" name="idm46734188852528"></a>

      Error number: <code class="literal">1657</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_many_values_error"><code class="literal">ER_TOO_MANY_VALUES_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot have more than one value for this type of %s
      partitioning
    </p></li><li class="listitem"><p><a name="error_er_row_single_partition_field_error"></a>
      <a class="indexterm" name="idm46734188846368"></a>

      <a class="indexterm" name="idm46734188845328"></a>

      Error number: <code class="literal">1658</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_row_single_partition_field_error"><code class="literal">ER_ROW_SINGLE_PARTITION_FIELD_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Row expressions in VALUES IN only allowed for multi-field
      column partitioning
    </p></li><li class="listitem"><p><a name="error_er_field_type_not_allowed_as_partition_field"></a>
      <a class="indexterm" name="idm46734188839184"></a>

      <a class="indexterm" name="idm46734188838144"></a>

      Error number: <code class="literal">1659</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_field_type_not_allowed_as_partition_field"><code class="literal">ER_FIELD_TYPE_NOT_ALLOWED_AS_PARTITION_FIELD</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Field '%s' is of a not allowed type for this type of
      partitioning
    </p></li><li class="listitem"><p><a name="error_er_partition_fields_too_long"></a>
      <a class="indexterm" name="idm46734188831904"></a>

      <a class="indexterm" name="idm46734188830864"></a>

      Error number: <code class="literal">1660</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_fields_too_long"><code class="literal">ER_PARTITION_FIELDS_TOO_LONG</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The total length of the partitioning fields is too large
    </p></li><li class="listitem"><p><a name="error_er_binlog_row_engine_and_stmt_engine"></a>
      <a class="indexterm" name="idm46734188824720"></a>

      <a class="indexterm" name="idm46734188823680"></a>

      Error number: <code class="literal">1661</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_row_engine_and_stmt_engine"><code class="literal">ER_BINLOG_ROW_ENGINE_AND_STMT_ENGINE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot execute statement: impossible to write to binary
      log since both row-incapable engines and statement-incapable
      engines are involved.
    </p></li><li class="listitem"><p><a name="error_er_binlog_row_mode_and_stmt_engine"></a>
      <a class="indexterm" name="idm46734188817408"></a>

      <a class="indexterm" name="idm46734188816368"></a>

      Error number: <code class="literal">1662</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_row_mode_and_stmt_engine"><code class="literal">ER_BINLOG_ROW_MODE_AND_STMT_ENGINE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot execute statement: impossible to write to binary
      log since BINLOG_FORMAT = ROW and at least one table uses a
      storage engine limited to statement-based logging.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_and_stmt_engine"></a>
      <a class="indexterm" name="idm46734188810128"></a>

      <a class="indexterm" name="idm46734188809024"></a>

      Error number: <code class="literal">1663</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_and_stmt_engine"><code class="literal">ER_BINLOG_UNSAFE_AND_STMT_ENGINE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot execute statement: impossible to write to binary
      log since statement is unsafe, storage engine is limited to
      statement-based logging, and BINLOG_FORMAT = MIXED. %s
    </p></li><li class="listitem"><p><a name="error_er_binlog_row_injection_and_stmt_engine"></a>
      <a class="indexterm" name="idm46734188802864"></a>

      <a class="indexterm" name="idm46734188801824"></a>

      Error number: <code class="literal">1664</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_row_injection_and_stmt_engine"><code class="literal">ER_BINLOG_ROW_INJECTION_AND_STMT_ENGINE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot execute statement: impossible to write to binary
      log since statement is in row format and at least one table uses a
      storage engine limited to statement-based logging.
    </p></li><li class="listitem"><p><a name="error_er_binlog_stmt_mode_and_row_engine"></a>
      <a class="indexterm" name="idm46734188795584"></a>

      <a class="indexterm" name="idm46734188794544"></a>

      Error number: <code class="literal">1665</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_stmt_mode_and_row_engine"><code class="literal">ER_BINLOG_STMT_MODE_AND_ROW_ENGINE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot execute statement: impossible to write to binary
      log since BINLOG_FORMAT = STATEMENT and at least one table uses a
      storage engine limited to row-based logging.%s
    </p></li><li class="listitem"><p><a name="error_er_binlog_row_injection_and_stmt_mode"></a>
      <a class="indexterm" name="idm46734188788240"></a>

      <a class="indexterm" name="idm46734188787200"></a>

      Error number: <code class="literal">1666</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_row_injection_and_stmt_mode"><code class="literal">ER_BINLOG_ROW_INJECTION_AND_STMT_MODE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot execute statement: impossible to write to binary
      log since statement is in row format and BINLOG_FORMAT =
      STATEMENT.
    </p></li><li class="listitem"><p><a name="error_er_binlog_multiple_engines_and_self_logging_engine"></a>
      <a class="indexterm" name="idm46734188780896"></a>

      <a class="indexterm" name="idm46734188779856"></a>

      Error number: <code class="literal">1667</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_multiple_engines_and_self_logging_engine"><code class="literal">ER_BINLOG_MULTIPLE_ENGINES_AND_SELF_LOGGING_ENGINE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot execute statement: impossible to write to binary
      log since more than one engine is involved and at least one engine
      is self-logging.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_limit"></a>
      <a class="indexterm" name="idm46734188773552"></a>

      <a class="indexterm" name="idm46734188772512"></a>

      Error number: <code class="literal">1668</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_limit"><code class="literal">ER_BINLOG_UNSAFE_LIMIT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The statement is unsafe because it uses a LIMIT clause.
      This is unsafe because the set of rows included cannot be
      predicted.
    </p></li><li class="listitem"><p><a name="error_er_unused4"></a>
      <a class="indexterm" name="idm46734188766416"></a>

      <a class="indexterm" name="idm46734188765376"></a>

      Error number: <code class="literal">1669</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unused4"><code class="literal">ER_UNUSED4</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The statement is unsafe because it uses INSERT DELAYED.
      This is unsafe because the times when rows are inserted cannot be
      predicted.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_system_table"></a>
      <a class="indexterm" name="idm46734188759328"></a>

      <a class="indexterm" name="idm46734188758224"></a>

      Error number: <code class="literal">1670</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_system_table"><code class="literal">ER_BINLOG_UNSAFE_SYSTEM_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The statement is unsafe because it uses the general log,
      slow query log, or performance_schema table(s). This is unsafe
      because system tables may differ on slaves.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_autoinc_columns"></a>
      <a class="indexterm" name="idm46734188752000"></a>

      <a class="indexterm" name="idm46734188750896"></a>

      Error number: <code class="literal">1671</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_autoinc_columns"><code class="literal">ER_BINLOG_UNSAFE_AUTOINC_COLUMNS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Statement is unsafe because it invokes a trigger or a
      stored function that inserts into an AUTO_INCREMENT column.
      Inserted values cannot be logged correctly.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_udf"></a>
      <a class="indexterm" name="idm46734188744672"></a>

      <a class="indexterm" name="idm46734188743632"></a>

      Error number: <code class="literal">1672</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_udf"><code class="literal">ER_BINLOG_UNSAFE_UDF</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Statement is unsafe because it uses a UDF which may not
      return the same value on the slave.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_system_variable"></a>
      <a class="indexterm" name="idm46734188737600"></a>

      <a class="indexterm" name="idm46734188736496"></a>

      Error number: <code class="literal">1673</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_system_variable"><code class="literal">ER_BINLOG_UNSAFE_SYSTEM_VARIABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Statement is unsafe because it uses a system variable
      that may have a different value on the slave.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_system_function"></a>
      <a class="indexterm" name="idm46734188730400"></a>

      <a class="indexterm" name="idm46734188729296"></a>

      Error number: <code class="literal">1674</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_system_function"><code class="literal">ER_BINLOG_UNSAFE_SYSTEM_FUNCTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Statement is unsafe because it uses a system function
      that may return a different value on the slave.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_nontrans_after_trans"></a>
      <a class="indexterm" name="idm46734188723216"></a>

      <a class="indexterm" name="idm46734188722176"></a>

      Error number: <code class="literal">1675</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_nontrans_after_trans"><code class="literal">ER_BINLOG_UNSAFE_NONTRANS_AFTER_TRANS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Statement is unsafe because it accesses a
      non-transactional table after accessing a transactional table
      within the same transaction.
    </p></li><li class="listitem"><p><a name="error_er_message_and_statement"></a>
      <a class="indexterm" name="idm46734188715968"></a>

      <a class="indexterm" name="idm46734188714928"></a>

      Error number: <code class="literal">1676</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_message_and_statement"><code class="literal">ER_MESSAGE_AND_STATEMENT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: %s Statement: %s
    </p></li><li class="listitem"><p><a name="error_er_slave_conversion_failed"></a>
      <a class="indexterm" name="idm46734188708944"></a>

      <a class="indexterm" name="idm46734188707904"></a>

      Error number: <code class="literal">1677</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_conversion_failed"><code class="literal">ER_SLAVE_CONVERSION_FAILED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Column %d of table '%s.%s' cannot be converted from type
      '%s' to type '%s'
    </p></li><li class="listitem"><p><a name="error_er_slave_cant_create_conversion"></a>
      <a class="indexterm" name="idm46734188701904"></a>

      <a class="indexterm" name="idm46734188700800"></a>

      Error number: <code class="literal">1678</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_cant_create_conversion"><code class="literal">ER_SLAVE_CANT_CREATE_CONVERSION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Can't create conversion table for table '%s.%s'
    </p></li><li class="listitem"><p><a name="error_er_inside_transaction_prevents_switch_binlog_format"></a>
      <a class="indexterm" name="idm46734188694688"></a>

      <a class="indexterm" name="idm46734188693648"></a>

      Error number: <code class="literal">1679</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_inside_transaction_prevents_switch_binlog_format"><code class="literal">ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_BINLOG_FORMAT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot modify @@session.binlog_format inside a
      transaction
    </p></li><li class="listitem"><p><a name="error_er_path_length"></a>
      <a class="indexterm" name="idm46734188687424"></a>

      <a class="indexterm" name="idm46734188686368"></a>

      Error number: <code class="literal">1680</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_path_length"><code class="literal">ER_PATH_LENGTH</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The path specified for %s is too long.
    </p></li><li class="listitem"><p><a name="error_er_warn_deprecated_syntax_no_replacement"></a>
      <a class="indexterm" name="idm46734188680384"></a>

      <a class="indexterm" name="idm46734188679344"></a>

      Error number: <code class="literal">1681</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_deprecated_syntax_no_replacement"><code class="literal">ER_WARN_DEPRECATED_SYNTAX_NO_REPLACEMENT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: '%s' is deprecated and will be removed in a future
      release.
    </p></li><li class="listitem"><p><a name="error_er_wrong_native_table_structure"></a>
      <a class="indexterm" name="idm46734188673248"></a>

      <a class="indexterm" name="idm46734188672144"></a>

      Error number: <code class="literal">1682</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_native_table_structure"><code class="literal">ER_WRONG_NATIVE_TABLE_STRUCTURE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Native table '%s'.'%s' has the wrong structure
    </p></li><li class="listitem"><p><a name="error_er_wrong_perfschema_usage"></a>
      <a class="indexterm" name="idm46734188666112"></a>

      <a class="indexterm" name="idm46734188665072"></a>

      Error number: <code class="literal">1683</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_perfschema_usage"><code class="literal">ER_WRONG_PERFSCHEMA_USAGE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Invalid performance_schema usage.
    </p></li><li class="listitem"><p><a name="error_er_warn_i_s_skipped_table"></a>
      <a class="indexterm" name="idm46734188659072"></a>

      <a class="indexterm" name="idm46734188658032"></a>

      Error number: <code class="literal">1684</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_i_s_skipped_table"><code class="literal">ER_WARN_I_S_SKIPPED_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Table '%s'.'%s' was skipped since its definition is being
      modified by concurrent DDL statement
    </p></li><li class="listitem"><p><a name="error_er_inside_transaction_prevents_switch_binlog_direct"></a>
      <a class="indexterm" name="idm46734188651792"></a>

      <a class="indexterm" name="idm46734188650752"></a>

      Error number: <code class="literal">1685</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_inside_transaction_prevents_switch_binlog_direct"><code class="literal">ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_BINLOG_DIRECT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot modify
      @@session.binlog_direct_non_transactional_updates inside a
      transaction
    </p></li><li class="listitem"><p><a name="error_er_stored_function_prevents_switch_binlog_direct"></a>
      <a class="indexterm" name="idm46734188644464"></a>

      <a class="indexterm" name="idm46734188643424"></a>

      Error number: <code class="literal">1686</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_stored_function_prevents_switch_binlog_direct"><code class="literal">ER_STORED_FUNCTION_PREVENTS_SWITCH_BINLOG_DIRECT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot change the binlog direct flag inside a stored
      function or trigger
    </p></li><li class="listitem"><p><a name="error_er_spatial_must_have_geom_col"></a>
      <a class="indexterm" name="idm46734188637376"></a>

      <a class="indexterm" name="idm46734188636272"></a>

      Error number: <code class="literal">1687</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_spatial_must_have_geom_col"><code class="literal">ER_SPATIAL_MUST_HAVE_GEOM_COL</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: A SPATIAL index may only contain a geometrical type
      column
    </p></li><li class="listitem"><p><a name="error_er_too_long_index_comment"></a>
      <a class="indexterm" name="idm46734188630224"></a>

      <a class="indexterm" name="idm46734188629184"></a>

      Error number: <code class="literal">1688</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_long_index_comment"><code class="literal">ER_TOO_LONG_INDEX_COMMENT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Comment for index '%s' is too long (max = %lu)
    </p></li><li class="listitem"><p><a name="error_er_lock_aborted"></a>
      <a class="indexterm" name="idm46734188623152"></a>

      <a class="indexterm" name="idm46734188622096"></a>

      Error number: <code class="literal">1689</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_lock_aborted"><code class="literal">ER_LOCK_ABORTED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Wait on a lock was aborted due to a pending exclusive
      lock
    </p></li><li class="listitem"><p><a name="error_er_data_out_of_range"></a>
      <a class="indexterm" name="idm46734188616176"></a>

      <a class="indexterm" name="idm46734188615136"></a>

      Error number: <code class="literal">1690</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_data_out_of_range"><code class="literal">ER_DATA_OUT_OF_RANGE</code></a>; SQLSTATE:
      <code class="literal">22003</code>
    </p><p>
      Message: %s value is out of range in '%s'
    </p></li><li class="listitem"><p><a name="error_er_wrong_spvar_type_in_limit"></a>
      <a class="indexterm" name="idm46734188609168"></a>

      <a class="indexterm" name="idm46734188608128"></a>

      Error number: <code class="literal">1691</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_spvar_type_in_limit"><code class="literal">ER_WRONG_SPVAR_TYPE_IN_LIMIT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: A variable of a non-integer based type in LIMIT clause
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_multiple_engines_and_self_logging_engine"></a>
      <a class="indexterm" name="idm46734188602048"></a>

      <a class="indexterm" name="idm46734188601008"></a>

      Error number: <code class="literal">1692</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_multiple_engines_and_self_logging_engine"><code class="literal">ER_BINLOG_UNSAFE_MULTIPLE_ENGINES_AND_SELF_LOGGING_ENGINE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Mixing self-logging and non-self-logging engines in a
      statement is unsafe.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_mixed_statement"></a>
      <a class="indexterm" name="idm46734188594832"></a>

      <a class="indexterm" name="idm46734188593728"></a>

      Error number: <code class="literal">1693</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_mixed_statement"><code class="literal">ER_BINLOG_UNSAFE_MIXED_STATEMENT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Statement accesses nontransactional table as well as
      transactional or temporary table, and writes to any of them.
    </p></li><li class="listitem"><p><a name="error_er_inside_transaction_prevents_switch_sql_log_bin"></a>
      <a class="indexterm" name="idm46734188587568"></a>

      <a class="indexterm" name="idm46734188586448"></a>

      Error number: <code class="literal">1694</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_inside_transaction_prevents_switch_sql_log_bin"><code class="literal">ER_INSIDE_TRANSACTION_PREVENTS_SWITCH_SQL_LOG_BIN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot modify @@session.sql_log_bin inside a transaction
    </p></li><li class="listitem"><p><a name="error_er_stored_function_prevents_switch_sql_log_bin"></a>
      <a class="indexterm" name="idm46734188580304"></a>

      <a class="indexterm" name="idm46734188579184"></a>

      Error number: <code class="literal">1695</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_stored_function_prevents_switch_sql_log_bin"><code class="literal">ER_STORED_FUNCTION_PREVENTS_SWITCH_SQL_LOG_BIN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot change the sql_log_bin inside a stored function or
      trigger
    </p></li><li class="listitem"><p><a name="error_er_failed_read_from_par_file"></a>
      <a class="indexterm" name="idm46734188573072"></a>

      <a class="indexterm" name="idm46734188572032"></a>

      Error number: <code class="literal">1696</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_failed_read_from_par_file"><code class="literal">ER_FAILED_READ_FROM_PAR_FILE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Failed to read from the .par file
    </p></li><li class="listitem"><p><a name="error_er_values_is_not_int_type_error"></a>
      <a class="indexterm" name="idm46734188565968"></a>

      <a class="indexterm" name="idm46734188564864"></a>

      Error number: <code class="literal">1697</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_values_is_not_int_type_error"><code class="literal">ER_VALUES_IS_NOT_INT_TYPE_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: VALUES value for partition '%s' must have type INT
    </p></li><li class="listitem"><p><a name="error_er_access_denied_no_password_error"></a>
      <a class="indexterm" name="idm46734188558848"></a>

      <a class="indexterm" name="idm46734188557808"></a>

      Error number: <code class="literal">1698</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_access_denied_no_password_error"><code class="literal">ER_ACCESS_DENIED_NO_PASSWORD_ERROR</code></a>;
      SQLSTATE: <code class="literal">28000</code>
    </p><p>
      Message: Access denied for user '%s'@'%s'
    </p></li><li class="listitem"><p><a name="error_er_set_password_auth_plugin"></a>
      <a class="indexterm" name="idm46734188551648"></a>

      <a class="indexterm" name="idm46734188550608"></a>

      Error number: <code class="literal">1699</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_set_password_auth_plugin"><code class="literal">ER_SET_PASSWORD_AUTH_PLUGIN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: SET PASSWORD has no significance for users authenticating
      via plugins
    </p></li><li class="listitem"><p><a name="error_er_grant_plugin_user_exists"></a>
      <a class="indexterm" name="idm46734188544496"></a>

      <a class="indexterm" name="idm46734188543456"></a>

      Error number: <code class="literal">1700</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_grant_plugin_user_exists"><code class="literal">ER_GRANT_PLUGIN_USER_EXISTS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: GRANT with IDENTIFIED WITH is illegal because the user
      %-.*s already exists
    </p></li><li class="listitem"><p><a name="error_er_truncate_illegal_fk"></a>
      <a class="indexterm" name="idm46734188537344"></a>

      <a class="indexterm" name="idm46734188536304"></a>

      Error number: <code class="literal">1701</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_truncate_illegal_fk"><code class="literal">ER_TRUNCATE_ILLEGAL_FK</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Cannot truncate a table referenced in a foreign key
      constraint (%s)
    </p></li><li class="listitem"><p><a name="error_er_plugin_is_permanent"></a>
      <a class="indexterm" name="idm46734188530224"></a>

      <a class="indexterm" name="idm46734188529184"></a>

      Error number: <code class="literal">1702</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_plugin_is_permanent"><code class="literal">ER_PLUGIN_IS_PERMANENT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Plugin '%s' is force_plus_permanent and can not be
      unloaded
    </p></li><li class="listitem"><p><a name="error_er_slave_heartbeat_value_out_of_range_min"></a>
      <a class="indexterm" name="idm46734188523136"></a>

      <a class="indexterm" name="idm46734188522096"></a>

      Error number: <code class="literal">1703</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_heartbeat_value_out_of_range_min"><code class="literal">ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE_MIN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The requested value for the heartbeat period is less than
      1 millisecond. The value is reset to 0, meaning that heartbeating
      will effectively be disabled.
    </p></li><li class="listitem"><p><a name="error_er_slave_heartbeat_value_out_of_range_max"></a>
      <a class="indexterm" name="idm46734188515840"></a>

      <a class="indexterm" name="idm46734188514800"></a>

      Error number: <code class="literal">1704</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_heartbeat_value_out_of_range_max"><code class="literal">ER_SLAVE_HEARTBEAT_VALUE_OUT_OF_RANGE_MAX</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The requested value for the heartbeat period exceeds the
      value of `slave_net_timeout' seconds. A sensible value for the
      period should be less than the timeout.
    </p></li><li class="listitem"><p><a name="error_er_stmt_cache_full"></a>
      <a class="indexterm" name="idm46734188508528"></a>

      <a class="indexterm" name="idm46734188507488"></a>

      Error number: <code class="literal">1705</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_stmt_cache_full"><code class="literal">ER_STMT_CACHE_FULL</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Multi-row statements required more than
      'max_binlog_stmt_cache_size' bytes of storage; increase this
      mysqld variable and try again
    </p></li><li class="listitem"><p><a name="error_er_multi_update_key_conflict"></a>
      <a class="indexterm" name="idm46734188501344"></a>

      <a class="indexterm" name="idm46734188500304"></a>

      Error number: <code class="literal">1706</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_multi_update_key_conflict"><code class="literal">ER_MULTI_UPDATE_KEY_CONFLICT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Primary key/partition key update is not allowed since the
      table is updated both as '%s' and '%s'.
    </p></li><li class="listitem"><p><a name="error_er_table_needs_rebuild"></a>
      <a class="indexterm" name="idm46734188494160"></a>

      <a class="indexterm" name="idm46734188493120"></a>

      Error number: <code class="literal">1707</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_needs_rebuild"><code class="literal">ER_TABLE_NEEDS_REBUILD</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Table rebuild required. Please do "ALTER TABLE `%s`
      FORCE" or dump/reload to fix it!
    </p></li><li class="listitem"><p><a name="error_warn_option_below_limit"></a>
      <a class="indexterm" name="idm46734188487024"></a>

      <a class="indexterm" name="idm46734188485984"></a>

      Error number: <code class="literal">1708</code>; Symbol:
      <a class="link" href="error-handling.html#error_warn_option_below_limit"><code class="literal">WARN_OPTION_BELOW_LIMIT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The value of '%s' should be no less than the value of
      '%s'
    </p></li><li class="listitem"><p><a name="error_er_index_column_too_long"></a>
      <a class="indexterm" name="idm46734188479984"></a>

      <a class="indexterm" name="idm46734188478944"></a>

      Error number: <code class="literal">1709</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_index_column_too_long"><code class="literal">ER_INDEX_COLUMN_TOO_LONG</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Index column size too large. The maximum column size is
      %lu bytes.
    </p></li><li class="listitem"><p><a name="error_er_error_in_trigger_body"></a>
      <a class="indexterm" name="idm46734188472896"></a>

      <a class="indexterm" name="idm46734188471856"></a>

      Error number: <code class="literal">1710</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_error_in_trigger_body"><code class="literal">ER_ERROR_IN_TRIGGER_BODY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Trigger '%s' has an error in its body: '%s'
    </p></li><li class="listitem"><p><a name="error_er_error_in_unknown_trigger_body"></a>
      <a class="indexterm" name="idm46734188465712"></a>

      <a class="indexterm" name="idm46734188464608"></a>

      Error number: <code class="literal">1711</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_error_in_unknown_trigger_body"><code class="literal">ER_ERROR_IN_UNKNOWN_TRIGGER_BODY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Unknown trigger has an error in its body: '%s'
    </p></li><li class="listitem"><p><a name="error_er_index_corrupt"></a>
      <a class="indexterm" name="idm46734188458688"></a>

      <a class="indexterm" name="idm46734188457632"></a>

      Error number: <code class="literal">1712</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_index_corrupt"><code class="literal">ER_INDEX_CORRUPT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Index %s is corrupted
    </p></li><li class="listitem"><p><a name="error_er_undo_record_too_big"></a>
      <a class="indexterm" name="idm46734188451632"></a>

      <a class="indexterm" name="idm46734188450592"></a>

      Error number: <code class="literal">1713</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_undo_record_too_big"><code class="literal">ER_UNDO_RECORD_TOO_BIG</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Undo log record is too big.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_insert_ignore_select"></a>
      <a class="indexterm" name="idm46734188444576"></a>

      <a class="indexterm" name="idm46734188443536"></a>

      Error number: <code class="literal">1714</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_insert_ignore_select"><code class="literal">ER_BINLOG_UNSAFE_INSERT_IGNORE_SELECT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: INSERT IGNORE... SELECT is unsafe because the order in
      which rows are retrieved by the SELECT determines which (if any)
      rows are ignored. This order cannot be predicted and may differ on
      master and the slave.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_insert_select_update"></a>
      <a class="indexterm" name="idm46734188437200"></a>

      <a class="indexterm" name="idm46734188436160"></a>

      Error number: <code class="literal">1715</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_insert_select_update"><code class="literal">ER_BINLOG_UNSAFE_INSERT_SELECT_UPDATE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: INSERT... SELECT... ON DUPLICATE KEY UPDATE is unsafe
      because the order in which rows are retrieved by the SELECT
      determines which (if any) rows are updated. This order cannot be
      predicted and may differ on master and the slave.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_replace_select"></a>
      <a class="indexterm" name="idm46734188429776"></a>

      <a class="indexterm" name="idm46734188428672"></a>

      Error number: <code class="literal">1716</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_replace_select"><code class="literal">ER_BINLOG_UNSAFE_REPLACE_SELECT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: REPLACE... SELECT is unsafe because the order in which
      rows are retrieved by the SELECT determines which (if any) rows
      are replaced. This order cannot be predicted and may differ on
      master and the slave.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_create_ignore_select"></a>
      <a class="indexterm" name="idm46734188422480"></a>

      <a class="indexterm" name="idm46734188421440"></a>

      Error number: <code class="literal">1717</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_create_ignore_select"><code class="literal">ER_BINLOG_UNSAFE_CREATE_IGNORE_SELECT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: CREATE... IGNORE SELECT is unsafe because the order in
      which rows are retrieved by the SELECT determines which (if any)
      rows are ignored. This order cannot be predicted and may differ on
      master and the slave.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_create_replace_select"></a>
      <a class="indexterm" name="idm46734188415216"></a>

      <a class="indexterm" name="idm46734188414176"></a>

      Error number: <code class="literal">1718</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_create_replace_select"><code class="literal">ER_BINLOG_UNSAFE_CREATE_REPLACE_SELECT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: CREATE... REPLACE SELECT is unsafe because the order in
      which rows are retrieved by the SELECT determines which (if any)
      rows are replaced. This order cannot be predicted and may differ
      on master and the slave.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_update_ignore"></a>
      <a class="indexterm" name="idm46734188407808"></a>

      <a class="indexterm" name="idm46734188406704"></a>

      Error number: <code class="literal">1719</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_update_ignore"><code class="literal">ER_BINLOG_UNSAFE_UPDATE_IGNORE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: UPDATE IGNORE is unsafe because the order in which rows
      are updated determines which (if any) rows are ignored. This order
      cannot be predicted and may differ on master and the slave.
    </p></li><li class="listitem"><p><a name="error_er_plugin_no_uninstall"></a>
      <a class="indexterm" name="idm46734188400592"></a>

      <a class="indexterm" name="idm46734188399552"></a>

      Error number: <code class="literal">1720</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_plugin_no_uninstall"><code class="literal">ER_PLUGIN_NO_UNINSTALL</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Plugin '%s' is marked as not dynamically uninstallable.
      You have to stop the server to uninstall it.
    </p></li><li class="listitem"><p><a name="error_er_plugin_no_install"></a>
      <a class="indexterm" name="idm46734188393440"></a>

      <a class="indexterm" name="idm46734188392400"></a>

      Error number: <code class="literal">1721</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_plugin_no_install"><code class="literal">ER_PLUGIN_NO_INSTALL</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Plugin '%s' is marked as not dynamically installable. You
      have to stop the server to install it.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_write_autoinc_select"></a>
      <a class="indexterm" name="idm46734188386240"></a>

      <a class="indexterm" name="idm46734188385200"></a>

      Error number: <code class="literal">1722</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_write_autoinc_select"><code class="literal">ER_BINLOG_UNSAFE_WRITE_AUTOINC_SELECT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Statements writing to a table with an auto-increment
      column after selecting from another table are unsafe because the
      order in which rows are retrieved determines what (if any) rows
      will be written. This order cannot be predicted and may differ on
      master and the slave.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_create_select_autoinc"></a>
      <a class="indexterm" name="idm46734188378848"></a>

      <a class="indexterm" name="idm46734188377808"></a>

      Error number: <code class="literal">1723</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_create_select_autoinc"><code class="literal">ER_BINLOG_UNSAFE_CREATE_SELECT_AUTOINC</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: CREATE TABLE... SELECT... on a table with an
      auto-increment column is unsafe because the order in which rows
      are retrieved by the SELECT determines which (if any) rows are
      inserted. This order cannot be predicted and may differ on master
      and the slave.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_insert_two_keys"></a>
      <a class="indexterm" name="idm46734188371520"></a>

      <a class="indexterm" name="idm46734188370416"></a>

      Error number: <code class="literal">1724</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_insert_two_keys"><code class="literal">ER_BINLOG_UNSAFE_INSERT_TWO_KEYS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: INSERT... ON DUPLICATE KEY UPDATE on a table with more
      than one UNIQUE KEY is unsafe
    </p></li><li class="listitem"><p><a name="error_er_table_in_fk_check"></a>
      <a class="indexterm" name="idm46734188364336"></a>

      <a class="indexterm" name="idm46734188363296"></a>

      Error number: <code class="literal">1725</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_in_fk_check"><code class="literal">ER_TABLE_IN_FK_CHECK</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Table is being used in foreign key check.
    </p></li><li class="listitem"><p><a name="error_er_unsupported_engine"></a>
      <a class="indexterm" name="idm46734188357248"></a>

      <a class="indexterm" name="idm46734188356208"></a>

      Error number: <code class="literal">1726</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unsupported_engine"><code class="literal">ER_UNSUPPORTED_ENGINE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Storage engine '%s' does not support system tables.
      [%s.%s]
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_autoinc_not_first"></a>
      <a class="indexterm" name="idm46734188350160"></a>

      <a class="indexterm" name="idm46734188349120"></a>

      Error number: <code class="literal">1727</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_autoinc_not_first"><code class="literal">ER_BINLOG_UNSAFE_AUTOINC_NOT_FIRST</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: INSERT into autoincrement field which is not the first
      part in the composed primary key is unsafe.
    </p></li><li class="listitem"><p><a name="error_er_cannot_load_from_table_v2"></a>
      <a class="indexterm" name="idm46734188342944"></a>

      <a class="indexterm" name="idm46734188341904"></a>

      Error number: <code class="literal">1728</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cannot_load_from_table_v2"><code class="literal">ER_CANNOT_LOAD_FROM_TABLE_V2</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot load from %s.%s. The table is probably corrupted
    </p></li><li class="listitem"><p><a name="error_er_master_delay_value_out_of_range"></a>
      <a class="indexterm" name="idm46734188335696"></a>

      <a class="indexterm" name="idm46734188334656"></a>

      Error number: <code class="literal">1729</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_master_delay_value_out_of_range"><code class="literal">ER_MASTER_DELAY_VALUE_OUT_OF_RANGE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The requested value %s for the master delay exceeds the
      maximum %u
    </p></li><li class="listitem"><p><a name="error_er_only_fd_and_rbr_events_allowed_in_binlog_statement"></a>
      <a class="indexterm" name="idm46734188328352"></a>

      <a class="indexterm" name="idm46734188327312"></a>

      Error number: <code class="literal">1730</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_only_fd_and_rbr_events_allowed_in_binlog_statement"><code class="literal">ER_ONLY_FD_AND_RBR_EVENTS_ALLOWED_IN_BINLOG_STATEMENT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Only Format_description_log_event and row events are
      allowed in BINLOG statements (but %s was provided)
    </p></li><li class="listitem"><p><a name="error_er_partition_exchange_different_option"></a>
      <a class="indexterm" name="idm46734188321008"></a>

      <a class="indexterm" name="idm46734188319968"></a>

      Error number: <code class="literal">1731</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_exchange_different_option"><code class="literal">ER_PARTITION_EXCHANGE_DIFFERENT_OPTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Non matching attribute '%s' between partition and table
    </p></li><li class="listitem"><p><a name="error_er_partition_exchange_part_table"></a>
      <a class="indexterm" name="idm46734188313840"></a>

      <a class="indexterm" name="idm46734188312736"></a>

      Error number: <code class="literal">1732</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_exchange_part_table"><code class="literal">ER_PARTITION_EXCHANGE_PART_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Table to exchange with partition is partitioned: '%s'
    </p></li><li class="listitem"><p><a name="error_er_partition_exchange_temp_table"></a>
      <a class="indexterm" name="idm46734188306688"></a>

      <a class="indexterm" name="idm46734188305584"></a>

      Error number: <code class="literal">1733</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_exchange_temp_table"><code class="literal">ER_PARTITION_EXCHANGE_TEMP_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Table to exchange with partition is temporary: '%s'
    </p></li><li class="listitem"><p><a name="error_er_partition_instead_of_subpartition"></a>
      <a class="indexterm" name="idm46734188299488"></a>

      <a class="indexterm" name="idm46734188298448"></a>

      Error number: <code class="literal">1734</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_instead_of_subpartition"><code class="literal">ER_PARTITION_INSTEAD_OF_SUBPARTITION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Subpartitioned table, use subpartition instead of
      partition
    </p></li><li class="listitem"><p><a name="error_er_unknown_partition"></a>
      <a class="indexterm" name="idm46734188292384"></a>

      <a class="indexterm" name="idm46734188291344"></a>

      Error number: <code class="literal">1735</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unknown_partition"><code class="literal">ER_UNKNOWN_PARTITION</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Unknown partition '%s' in table '%s'
    </p></li><li class="listitem"><p><a name="error_er_tables_different_metadata"></a>
      <a class="indexterm" name="idm46734188285376"></a>

      <a class="indexterm" name="idm46734188284336"></a>

      Error number: <code class="literal">1736</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_tables_different_metadata"><code class="literal">ER_TABLES_DIFFERENT_METADATA</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Tables have different definitions
    </p></li><li class="listitem"><p><a name="error_er_row_does_not_match_partition"></a>
      <a class="indexterm" name="idm46734188278336"></a>

      <a class="indexterm" name="idm46734188277232"></a>

      Error number: <code class="literal">1737</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_row_does_not_match_partition"><code class="literal">ER_ROW_DOES_NOT_MATCH_PARTITION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Found a row that does not match the partition
    </p></li><li class="listitem"><p><a name="error_er_binlog_cache_size_greater_than_max"></a>
      <a class="indexterm" name="idm46734188271152"></a>

      <a class="indexterm" name="idm46734188270112"></a>

      Error number: <code class="literal">1738</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_cache_size_greater_than_max"><code class="literal">ER_BINLOG_CACHE_SIZE_GREATER_THAN_MAX</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Option binlog_cache_size (%lu) is greater than
      max_binlog_cache_size (%lu); setting binlog_cache_size equal to
      max_binlog_cache_size.
    </p></li><li class="listitem"><p><a name="error_er_warn_index_not_applicable"></a>
      <a class="indexterm" name="idm46734188263968"></a>

      <a class="indexterm" name="idm46734188262928"></a>

      Error number: <code class="literal">1739</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_index_not_applicable"><code class="literal">ER_WARN_INDEX_NOT_APPLICABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot use %s access on index '%s' due to type or
      collation conversion on field '%s'
    </p></li><li class="listitem"><p><a name="error_er_partition_exchange_foreign_key"></a>
      <a class="indexterm" name="idm46734188256864"></a>

      <a class="indexterm" name="idm46734188255760"></a>

      Error number: <code class="literal">1740</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_exchange_foreign_key"><code class="literal">ER_PARTITION_EXCHANGE_FOREIGN_KEY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Table to exchange with partition has foreign key
      references: '%s'
    </p></li><li class="listitem"><p><a name="error_er_no_such_key_value"></a>
      <a class="indexterm" name="idm46734188249632"></a>

      <a class="indexterm" name="idm46734188248592"></a>

      Error number: <code class="literal">1741</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_such_key_value"><code class="literal">ER_NO_SUCH_KEY_VALUE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Key value '%s' was not found in table '%s.%s'
    </p></li><li class="listitem"><p><a name="error_er_rpl_info_data_too_long"></a>
      <a class="indexterm" name="idm46734188242544"></a>

      <a class="indexterm" name="idm46734188241504"></a>

      Error number: <code class="literal">1742</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_rpl_info_data_too_long"><code class="literal">ER_RPL_INFO_DATA_TOO_LONG</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Data for column '%s' too long
    </p></li><li class="listitem"><p><a name="error_er_network_read_event_checksum_failure"></a>
      <a class="indexterm" name="idm46734188235456"></a>

      <a class="indexterm" name="idm46734188234416"></a>

      Error number: <code class="literal">1743</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_network_read_event_checksum_failure"><code class="literal">ER_NETWORK_READ_EVENT_CHECKSUM_FAILURE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Replication event checksum verification failed while
      reading from network.
    </p></li><li class="listitem"><p><a name="error_er_binlog_read_event_checksum_failure"></a>
      <a class="indexterm" name="idm46734188228288"></a>

      <a class="indexterm" name="idm46734188227248"></a>

      Error number: <code class="literal">1744</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_read_event_checksum_failure"><code class="literal">ER_BINLOG_READ_EVENT_CHECKSUM_FAILURE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Replication event checksum verification failed while
      reading from a log file.
    </p></li><li class="listitem"><p><a name="error_er_binlog_stmt_cache_size_greater_than_max"></a>
      <a class="indexterm" name="idm46734188221104"></a>

      <a class="indexterm" name="idm46734188220064"></a>

      Error number: <code class="literal">1745</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_stmt_cache_size_greater_than_max"><code class="literal">ER_BINLOG_STMT_CACHE_SIZE_GREATER_THAN_MAX</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Option binlog_stmt_cache_size (%lu) is greater than
      max_binlog_stmt_cache_size (%lu); setting binlog_stmt_cache_size
      equal to max_binlog_stmt_cache_size.
    </p></li><li class="listitem"><p><a name="error_er_cant_update_table_in_create_table_select"></a>
      <a class="indexterm" name="idm46734188213680"></a>

      <a class="indexterm" name="idm46734188212640"></a>

      Error number: <code class="literal">1746</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_update_table_in_create_table_select"><code class="literal">ER_CANT_UPDATE_TABLE_IN_CREATE_TABLE_SELECT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Can't update table '%s' while '%s' is being created.
    </p></li><li class="listitem"><p><a name="error_er_partition_clause_on_nonpartitioned"></a>
      <a class="indexterm" name="idm46734188206496"></a>

      <a class="indexterm" name="idm46734188205456"></a>

      Error number: <code class="literal">1747</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_clause_on_nonpartitioned"><code class="literal">ER_PARTITION_CLAUSE_ON_NONPARTITIONED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: PARTITION () clause on non partitioned table
    </p></li><li class="listitem"><p><a name="error_er_row_does_not_match_given_partition_set"></a>
      <a class="indexterm" name="idm46734188199408"></a>

      <a class="indexterm" name="idm46734188198368"></a>

      Error number: <code class="literal">1748</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_row_does_not_match_given_partition_set"><code class="literal">ER_ROW_DOES_NOT_MATCH_GIVEN_PARTITION_SET</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Found a row not matching the given partition set
    </p></li><li class="listitem"><p><a name="error_er_no_such_partition__unused"></a>
      <a class="indexterm" name="idm46734188192352"></a>

      <a class="indexterm" name="idm46734188191312"></a>

      Error number: <code class="literal">1749</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_such_partition__unused"><code class="literal">ER_NO_SUCH_PARTITION__UNUSED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: partition '%s' doesn't exist
    </p></li><li class="listitem"><p><a name="error_er_change_rpl_info_repository_failure"></a>
      <a class="indexterm" name="idm46734188185200"></a>

      <a class="indexterm" name="idm46734188184160"></a>

      Error number: <code class="literal">1750</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_change_rpl_info_repository_failure"><code class="literal">ER_CHANGE_RPL_INFO_REPOSITORY_FAILURE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Failure while changing the type of replication
      repository: %s.
    </p></li><li class="listitem"><p><a name="error_er_warning_not_complete_rollback_with_created_temp_table"></a>
      <a class="indexterm" name="idm46734188177920"></a>

      <a class="indexterm" name="idm46734188176880"></a>

      Error number: <code class="literal">1751</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warning_not_complete_rollback_with_created_temp_table"><code class="literal">ER_WARNING_NOT_COMPLETE_ROLLBACK_WITH_CREATED_TEMP_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The creation of some temporary tables could not be rolled
      back.
    </p></li><li class="listitem"><p><a name="error_er_warning_not_complete_rollback_with_dropped_temp_table"></a>
      <a class="indexterm" name="idm46734188170608"></a>

      <a class="indexterm" name="idm46734188169568"></a>

      Error number: <code class="literal">1752</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warning_not_complete_rollback_with_dropped_temp_table"><code class="literal">ER_WARNING_NOT_COMPLETE_ROLLBACK_WITH_DROPPED_TEMP_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Some temporary tables were dropped, but these operations
      could not be rolled back.
    </p></li><li class="listitem"><p><a name="error_er_mts_feature_is_not_supported"></a>
      <a class="indexterm" name="idm46734188163248"></a>

      <a class="indexterm" name="idm46734188162144"></a>

      Error number: <code class="literal">1753</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_mts_feature_is_not_supported"><code class="literal">ER_MTS_FEATURE_IS_NOT_SUPPORTED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: %s is not supported in multi-threaded slave mode. %s
    </p></li><li class="listitem"><p><a name="error_er_mts_updated_dbs_greater_max"></a>
      <a class="indexterm" name="idm46734188156096"></a>

      <a class="indexterm" name="idm46734188154992"></a>

      Error number: <code class="literal">1754</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_mts_updated_dbs_greater_max"><code class="literal">ER_MTS_UPDATED_DBS_GREATER_MAX</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The number of modified databases exceeds the maximum %d;
      the database names will not be included in the replication event
      metadata.
    </p></li><li class="listitem"><p><a name="error_er_mts_cant_parallel"></a>
      <a class="indexterm" name="idm46734188148928"></a>

      <a class="indexterm" name="idm46734188147888"></a>

      Error number: <code class="literal">1755</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_mts_cant_parallel"><code class="literal">ER_MTS_CANT_PARALLEL</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Cannot execute the current event group in the parallel
      mode. Encountered event %s, relay-log name %s, position %s which
      prevents execution of this event group in parallel mode. Reason:
      %s.
    </p></li><li class="listitem"><p><a name="error_er_mts_inconsistent_data"></a>
      <a class="indexterm" name="idm46734188141744"></a>

      <a class="indexterm" name="idm46734188140704"></a>

      Error number: <code class="literal">1756</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_mts_inconsistent_data"><code class="literal">ER_MTS_INCONSISTENT_DATA</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: %s
    </p></li><li class="listitem"><p><a name="error_er_fulltext_not_supported_with_partitioning"></a>
      <a class="indexterm" name="idm46734188134688"></a>

      <a class="indexterm" name="idm46734188133648"></a>

      Error number: <code class="literal">1757</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fulltext_not_supported_with_partitioning"><code class="literal">ER_FULLTEXT_NOT_SUPPORTED_WITH_PARTITIONING</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: FULLTEXT index is not supported for partitioned tables.
    </p></li><li class="listitem"><p><a name="error_er_da_invalid_condition_number"></a>
      <a class="indexterm" name="idm46734188127488"></a>

      <a class="indexterm" name="idm46734188126384"></a>

      Error number: <code class="literal">1758</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_da_invalid_condition_number"><code class="literal">ER_DA_INVALID_CONDITION_NUMBER</code></a>;
      SQLSTATE: <code class="literal">35000</code>
    </p><p>
      Message: Invalid condition number
    </p></li><li class="listitem"><p><a name="error_er_insecure_plain_text"></a>
      <a class="indexterm" name="idm46734188120304"></a>

      <a class="indexterm" name="idm46734188119264"></a>

      Error number: <code class="literal">1759</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_insecure_plain_text"><code class="literal">ER_INSECURE_PLAIN_TEXT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Sending passwords in plain text without SSL/TLS is
      extremely insecure.
    </p></li><li class="listitem"><p><a name="error_er_insecure_change_master"></a>
      <a class="indexterm" name="idm46734188113184"></a>

      <a class="indexterm" name="idm46734188112144"></a>

      Error number: <code class="literal">1760</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_insecure_change_master"><code class="literal">ER_INSECURE_CHANGE_MASTER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Storing MySQL user name or password information in the
      master info repository is not secure and is therefore not
      recommended. Please consider using the USER and PASSWORD
      connection options for START SLAVE; see the 'START SLAVE Syntax'
      in the MySQL Manual for more information.
    </p></li><li class="listitem"><p><a name="error_er_foreign_duplicate_key_with_child_info"></a>
      <a class="indexterm" name="idm46734188105696"></a>

      <a class="indexterm" name="idm46734188104656"></a>

      Error number: <code class="literal">1761</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_foreign_duplicate_key_with_child_info"><code class="literal">ER_FOREIGN_DUPLICATE_KEY_WITH_CHILD_INFO</code></a>;
      SQLSTATE: <code class="literal">23000</code>
    </p><p>
      Message: Foreign key constraint for table '%s', record '%s' would
      lead to a duplicate entry in table '%s', key '%s'
    </p></li><li class="listitem"><p><a name="error_er_foreign_duplicate_key_without_child_info"></a>
      <a class="indexterm" name="idm46734188098400"></a>

      <a class="indexterm" name="idm46734188097360"></a>

      Error number: <code class="literal">1762</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_foreign_duplicate_key_without_child_info"><code class="literal">ER_FOREIGN_DUPLICATE_KEY_WITHOUT_CHILD_INFO</code></a>;
      SQLSTATE: <code class="literal">23000</code>
    </p><p>
      Message: Foreign key constraint for table '%s', record '%s' would
      lead to a duplicate entry in a child table
    </p></li><li class="listitem"><p><a name="error_er_sqlthread_with_secure_slave"></a>
      <a class="indexterm" name="idm46734188091216"></a>

      <a class="indexterm" name="idm46734188090112"></a>

      Error number: <code class="literal">1763</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sqlthread_with_secure_slave"><code class="literal">ER_SQLTHREAD_WITH_SECURE_SLAVE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Setting authentication options is not possible when only
      the Slave SQL Thread is being started.
    </p></li><li class="listitem"><p><a name="error_er_table_has_no_ft"></a>
      <a class="indexterm" name="idm46734188084016"></a>

      <a class="indexterm" name="idm46734188082976"></a>

      Error number: <code class="literal">1764</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_has_no_ft"><code class="literal">ER_TABLE_HAS_NO_FT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The table does not have FULLTEXT index to support this
      query
    </p></li><li class="listitem"><p><a name="error_er_variable_not_settable_in_sf_or_trigger"></a>
      <a class="indexterm" name="idm46734188076800"></a>

      <a class="indexterm" name="idm46734188075760"></a>

      Error number: <code class="literal">1765</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_variable_not_settable_in_sf_or_trigger"><code class="literal">ER_VARIABLE_NOT_SETTABLE_IN_SF_OR_TRIGGER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The system variable %s cannot be set in stored functions
      or triggers.
    </p></li><li class="listitem"><p><a name="error_er_variable_not_settable_in_transaction"></a>
      <a class="indexterm" name="idm46734188069536"></a>

      <a class="indexterm" name="idm46734188068496"></a>

      Error number: <code class="literal">1766</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_variable_not_settable_in_transaction"><code class="literal">ER_VARIABLE_NOT_SETTABLE_IN_TRANSACTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The system variable %s cannot be set when there is an
      ongoing transaction.
    </p></li><li class="listitem"><p><a name="error_er_gtid_next_is_not_in_gtid_next_list"></a>
      <a class="indexterm" name="idm46734188062368"></a>

      <a class="indexterm" name="idm46734188061328"></a>

      Error number: <code class="literal">1767</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gtid_next_is_not_in_gtid_next_list"><code class="literal">ER_GTID_NEXT_IS_NOT_IN_GTID_NEXT_LIST</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The system variable @@SESSION.GTID_NEXT has the value %s,
      which is not listed in @@SESSION.GTID_NEXT_LIST.
    </p></li><li class="listitem"><p><a name="error_er_cant_change_gtid_next_in_transaction_when_gtid_next_list_is_null"></a>
      <a class="indexterm" name="idm46734188055072"></a>

      <a class="indexterm" name="idm46734188053920"></a>

      Error number: <code class="literal">1768</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_change_gtid_next_in_transaction_when_gtid_next_list_is_null"><code class="literal">ER_CANT_CHANGE_GTID_NEXT_IN_TRANSACTION_WHEN_GTID_NEXT_LIST_IS_NULL</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The system variable @@SESSION.GTID_NEXT cannot change
      inside a transaction.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cant_change_gtid_next_in_transaction_when_gtid_next_list_is_null"><code class="literal">ER_CANT_CHANGE_GTID_NEXT_IN_TRANSACTION_WHEN_GTID_NEXT_LIST_IS_NULL</code></a>
      was removed after 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_cant_change_gtid_next_in_transaction"></a>
      <a class="indexterm" name="idm46734188045792"></a>

      <a class="indexterm" name="idm46734188044752"></a>

      Error number: <code class="literal">1768</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_change_gtid_next_in_transaction"><code class="literal">ER_CANT_CHANGE_GTID_NEXT_IN_TRANSACTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The system variable @@SESSION.GTID_NEXT cannot change
      inside a transaction.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cant_change_gtid_next_in_transaction"><code class="literal">ER_CANT_CHANGE_GTID_NEXT_IN_TRANSACTION</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_set_statement_cannot_invoke_function"></a>
      <a class="indexterm" name="idm46734188036848"></a>

      <a class="indexterm" name="idm46734188035808"></a>

      Error number: <code class="literal">1769</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_set_statement_cannot_invoke_function"><code class="literal">ER_SET_STATEMENT_CANNOT_INVOKE_FUNCTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The statement 'SET %s' cannot invoke a stored function.
    </p></li><li class="listitem"><p><a name="error_er_gtid_next_cant_be_automatic_if_gtid_next_list_is_non_null"></a>
      <a class="indexterm" name="idm46734188029744"></a>

      <a class="indexterm" name="idm46734188028704"></a>

      Error number: <code class="literal">1770</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gtid_next_cant_be_automatic_if_gtid_next_list_is_non_null"><code class="literal">ER_GTID_NEXT_CANT_BE_AUTOMATIC_IF_GTID_NEXT_LIST_IS_NON_NULL</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The system variable @@SESSION.GTID_NEXT cannot be
      'AUTOMATIC' when @@SESSION.GTID_NEXT_LIST is non-NULL.
    </p></li><li class="listitem"><p><a name="error_er_skipping_logged_transaction"></a>
      <a class="indexterm" name="idm46734188022496"></a>

      <a class="indexterm" name="idm46734188021392"></a>

      Error number: <code class="literal">1771</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_skipping_logged_transaction"><code class="literal">ER_SKIPPING_LOGGED_TRANSACTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Skipping transaction %s because it has already been
      executed and logged.
    </p></li><li class="listitem"><p><a name="error_er_malformed_gtid_set_specification"></a>
      <a class="indexterm" name="idm46734188015280"></a>

      <a class="indexterm" name="idm46734188014240"></a>

      Error number: <code class="literal">1772</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_malformed_gtid_set_specification"><code class="literal">ER_MALFORMED_GTID_SET_SPECIFICATION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Malformed GTID set specification '%s'.
    </p></li><li class="listitem"><p><a name="error_er_malformed_gtid_set_encoding"></a>
      <a class="indexterm" name="idm46734188008128"></a>

      <a class="indexterm" name="idm46734188007024"></a>

      Error number: <code class="literal">1773</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_malformed_gtid_set_encoding"><code class="literal">ER_MALFORMED_GTID_SET_ENCODING</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Malformed GTID set encoding.
    </p></li><li class="listitem"><p><a name="error_er_malformed_gtid_specification"></a>
      <a class="indexterm" name="idm46734188001008"></a>

      <a class="indexterm" name="idm46734187999904"></a>

      Error number: <code class="literal">1774</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_malformed_gtid_specification"><code class="literal">ER_MALFORMED_GTID_SPECIFICATION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Malformed GTID specification '%s'.
    </p></li><li class="listitem"><p><a name="error_er_gno_exhausted"></a>
      <a class="indexterm" name="idm46734187994000"></a>

      <a class="indexterm" name="idm46734187992944"></a>

      Error number: <code class="literal">1775</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gno_exhausted"><code class="literal">ER_GNO_EXHAUSTED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Impossible to generate Global Transaction Identifier: the
      integer component reached the maximal value. Restart the server
      with a new server_uuid.
    </p></li><li class="listitem"><p><a name="error_er_bad_slave_auto_position"></a>
      <a class="indexterm" name="idm46734187986752"></a>

      <a class="indexterm" name="idm46734187985712"></a>

      Error number: <code class="literal">1776</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_bad_slave_auto_position"><code class="literal">ER_BAD_SLAVE_AUTO_POSITION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Parameters MASTER_LOG_FILE, MASTER_LOG_POS,
      RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when
      MASTER_AUTO_POSITION is active.
    </p></li><li class="listitem"><p><a name="error_er_auto_position_requires_gtid_mode_on"></a>
      <a class="indexterm" name="idm46734187979488"></a>

      <a class="indexterm" name="idm46734187978448"></a>

      Error number: <code class="literal">1777</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_auto_position_requires_gtid_mode_on"><code class="literal">ER_AUTO_POSITION_REQUIRES_GTID_MODE_ON</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: CHANGE MASTER TO MASTER_AUTO_POSITION = 1 can only be
      executed when @@GLOBAL.GTID_MODE = ON.
    </p><p>
      <a class="link" href="error-handling.html#error_er_auto_position_requires_gtid_mode_on"><code class="literal">ER_AUTO_POSITION_REQUIRES_GTID_MODE_ON</code></a>
      was removed after 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_auto_position_requires_gtid_mode_not_off"></a>
      <a class="indexterm" name="idm46734187970592"></a>

      <a class="indexterm" name="idm46734187969552"></a>

      Error number: <code class="literal">1777</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_auto_position_requires_gtid_mode_not_off"><code class="literal">ER_AUTO_POSITION_REQUIRES_GTID_MODE_NOT_OFF</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: CHANGE MASTER TO MASTER_AUTO_POSITION = 1 cannot be
      executed because @@GLOBAL.GTID_MODE = OFF.
    </p><p>
      <a class="link" href="error-handling.html#error_er_auto_position_requires_gtid_mode_not_off"><code class="literal">ER_AUTO_POSITION_REQUIRES_GTID_MODE_NOT_OFF</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_cant_do_implicit_commit_in_trx_when_gtid_next_is_set"></a>
      <a class="indexterm" name="idm46734187961520"></a>

      <a class="indexterm" name="idm46734187960480"></a>

      Error number: <code class="literal">1778</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_do_implicit_commit_in_trx_when_gtid_next_is_set"><code class="literal">ER_CANT_DO_IMPLICIT_COMMIT_IN_TRX_WHEN_GTID_NEXT_IS_SET</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot execute statements with implicit commit inside a
      transaction when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.
    </p></li><li class="listitem"><p><a name="error_er_gtid_mode_2_or_3_requires_enforce_gtid_consistency_on"></a>
      <a class="indexterm" name="idm46734187954176"></a>

      <a class="indexterm" name="idm46734187953136"></a>

      Error number: <code class="literal">1779</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gtid_mode_2_or_3_requires_enforce_gtid_consistency_on"><code class="literal">ER_GTID_MODE_2_OR_3_REQUIRES_ENFORCE_GTID_CONSISTENCY_ON</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: @@GLOBAL.GTID_MODE = ON or UPGRADE_STEP_2 requires
      @@GLOBAL.ENFORCE_GTID_CONSISTENCY = 1.
    </p><p>
      <a class="link" href="error-handling.html#error_er_gtid_mode_2_or_3_requires_enforce_gtid_consistency_on"><code class="literal">ER_GTID_MODE_2_OR_3_REQUIRES_ENFORCE_GTID_CONSISTENCY_ON</code></a>
      was removed after 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_gtid_mode_on_requires_enforce_gtid_consistency_on"></a>
      <a class="indexterm" name="idm46734187945056"></a>

      <a class="indexterm" name="idm46734187944016"></a>

      Error number: <code class="literal">1779</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gtid_mode_on_requires_enforce_gtid_consistency_on"><code class="literal">ER_GTID_MODE_ON_REQUIRES_ENFORCE_GTID_CONSISTENCY_ON</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: GTID_MODE = ON requires ENFORCE_GTID_CONSISTENCY = ON.
    </p><p>
      <a class="link" href="error-handling.html#error_er_gtid_mode_on_requires_enforce_gtid_consistency_on"><code class="literal">ER_GTID_MODE_ON_REQUIRES_ENFORCE_GTID_CONSISTENCY_ON</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_gtid_mode_requires_binlog"></a>
      <a class="indexterm" name="idm46734187935984"></a>

      <a class="indexterm" name="idm46734187934944"></a>

      Error number: <code class="literal">1780</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gtid_mode_requires_binlog"><code class="literal">ER_GTID_MODE_REQUIRES_BINLOG</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: @@GLOBAL.GTID_MODE = ON or ON_PERMISSIVE or
      OFF_PERMISSIVE requires --log-bin and --log-slave-updates.
    </p></li><li class="listitem"><p><a name="error_er_cant_set_gtid_next_to_gtid_when_gtid_mode_is_off"></a>
      <a class="indexterm" name="idm46734187928784"></a>

      <a class="indexterm" name="idm46734187927744"></a>

      Error number: <code class="literal">1781</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_set_gtid_next_to_gtid_when_gtid_mode_is_off"><code class="literal">ER_CANT_SET_GTID_NEXT_TO_GTID_WHEN_GTID_MODE_IS_OFF</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: @@SESSION.GTID_NEXT cannot be set to UUID:NUMBER when
      @@GLOBAL.GTID_MODE = OFF.
    </p></li><li class="listitem"><p><a name="error_er_cant_set_gtid_next_to_anonymous_when_gtid_mode_is_on"></a>
      <a class="indexterm" name="idm46734187921424"></a>

      <a class="indexterm" name="idm46734187920384"></a>

      Error number: <code class="literal">1782</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_set_gtid_next_to_anonymous_when_gtid_mode_is_on"><code class="literal">ER_CANT_SET_GTID_NEXT_TO_ANONYMOUS_WHEN_GTID_MODE_IS_ON</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: @@SESSION.GTID_NEXT cannot be set to ANONYMOUS when
      @@GLOBAL.GTID_MODE = ON.
    </p></li><li class="listitem"><p><a name="error_er_cant_set_gtid_next_list_to_non_null_when_gtid_mode_is_off"></a>
      <a class="indexterm" name="idm46734187914144"></a>

      <a class="indexterm" name="idm46734187913104"></a>

      Error number: <code class="literal">1783</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_set_gtid_next_list_to_non_null_when_gtid_mode_is_off"><code class="literal">ER_CANT_SET_GTID_NEXT_LIST_TO_NON_NULL_WHEN_GTID_MODE_IS_OFF</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: @@SESSION.GTID_NEXT_LIST cannot be set to a non-NULL
      value when @@GLOBAL.GTID_MODE = OFF.
    </p></li><li class="listitem"><p><a name="error_er_found_gtid_event_when_gtid_mode_is_off"></a>
      <a class="indexterm" name="idm46734187906736"></a>

      <a class="indexterm" name="idm46734187905696"></a>

      Error number: <code class="literal">1784</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_found_gtid_event_when_gtid_mode_is_off"><code class="literal">ER_FOUND_GTID_EVENT_WHEN_GTID_MODE_IS_OFF</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Found a Gtid_log_event or Previous_gtids_log_event when
      @@GLOBAL.GTID_MODE = OFF.
    </p><p>
      <a class="link" href="error-handling.html#error_er_found_gtid_event_when_gtid_mode_is_off"><code class="literal">ER_FOUND_GTID_EVENT_WHEN_GTID_MODE_IS_OFF</code></a>
      was removed after 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_found_gtid_event_when_gtid_mode_is_off__unused"></a>
      <a class="indexterm" name="idm46734187897728"></a>

      <a class="indexterm" name="idm46734187896608"></a>

      Error number: <code class="literal">1784</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_found_gtid_event_when_gtid_mode_is_off__unused"><code class="literal">ER_FOUND_GTID_EVENT_WHEN_GTID_MODE_IS_OFF__UNUSED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Found a Gtid_log_event when @@GLOBAL.GTID_MODE = OFF.
    </p><p>
      <a class="link" href="error-handling.html#error_er_found_gtid_event_when_gtid_mode_is_off__unused"><code class="literal">ER_FOUND_GTID_EVENT_WHEN_GTID_MODE_IS_OFF__UNUSED</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_gtid_unsafe_non_transactional_table"></a>
      <a class="indexterm" name="idm46734187888800"></a>

      <a class="indexterm" name="idm46734187887760"></a>

      Error number: <code class="literal">1785</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gtid_unsafe_non_transactional_table"><code class="literal">ER_GTID_UNSAFE_NON_TRANSACTIONAL_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Statement violates GTID consistency: Updates to
      non-transactional tables can only be done in either autocommitted
      statements or single-statement transactions, and never in the same
      statement as updates to transactional tables.
    </p></li><li class="listitem"><p><a name="error_er_gtid_unsafe_create_select"></a>
      <a class="indexterm" name="idm46734187881504"></a>

      <a class="indexterm" name="idm46734187880464"></a>

      Error number: <code class="literal">1786</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gtid_unsafe_create_select"><code class="literal">ER_GTID_UNSAFE_CREATE_SELECT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Statement violates GTID consistency: CREATE TABLE ...
      SELECT.
    </p></li><li class="listitem"><p><a name="error_er_gtid_unsafe_create_drop_temporary_table_in_transaction"></a>
      <a class="indexterm" name="idm46734187874320"></a>

      <a class="indexterm" name="idm46734187873280"></a>

      Error number: <code class="literal">1787</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gtid_unsafe_create_drop_temporary_table_in_transaction"><code class="literal">ER_GTID_UNSAFE_CREATE_DROP_TEMPORARY_TABLE_IN_TRANSACTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Statement violates GTID consistency: CREATE TEMPORARY
      TABLE and DROP TEMPORARY TABLE can only be executed outside
      transactional context. These statements are also not allowed in a
      function or trigger because functions and triggers are also
      considered to be multi-statement transactions.
    </p></li><li class="listitem"><p><a name="error_er_gtid_mode_can_only_change_one_step_at_a_time"></a>
      <a class="indexterm" name="idm46734187866752"></a>

      <a class="indexterm" name="idm46734187865632"></a>

      Error number: <code class="literal">1788</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gtid_mode_can_only_change_one_step_at_a_time"><code class="literal">ER_GTID_MODE_CAN_ONLY_CHANGE_ONE_STEP_AT_A_TIME</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The value of @@GLOBAL.GTID_MODE can only be changed one
      step at a time: OFF &lt;-&gt; OFF_PERMISSIVE &lt;-&gt;
      ON_PERMISSIVE &lt;-&gt; ON. Also note that this value must be
      stepped up or down simultaneously on all servers. See the Manual
      for instructions.
    </p></li><li class="listitem"><p><a name="error_er_master_has_purged_required_gtids"></a>
      <a class="indexterm" name="idm46734187858960"></a>

      <a class="indexterm" name="idm46734187857920"></a>

      Error number: <code class="literal">1789</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_master_has_purged_required_gtids"><code class="literal">ER_MASTER_HAS_PURGED_REQUIRED_GTIDS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The slave is connecting using CHANGE MASTER TO
      MASTER_AUTO_POSITION = 1, but the master has purged binary logs
      containing GTIDs that the slave requires. Replicate the missing
      transactions from elsewhere, or provision a new slave from backup.
      Consider increasing the master's binary log expiration period. %s.
    </p></li><li class="listitem"><p><a name="error_er_cant_set_gtid_next_when_owning_gtid"></a>
      <a class="indexterm" name="idm46734187851472"></a>

      <a class="indexterm" name="idm46734187850432"></a>

      Error number: <code class="literal">1790</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_set_gtid_next_when_owning_gtid"><code class="literal">ER_CANT_SET_GTID_NEXT_WHEN_OWNING_GTID</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: @@SESSION.GTID_NEXT cannot be changed by a client that
      owns a GTID. The client owns %s. Ownership is released on COMMIT
      or ROLLBACK.
    </p></li><li class="listitem"><p><a name="error_er_unknown_explain_format"></a>
      <a class="indexterm" name="idm46734187844288"></a>

      <a class="indexterm" name="idm46734187843248"></a>

      Error number: <code class="literal">1791</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unknown_explain_format"><code class="literal">ER_UNKNOWN_EXPLAIN_FORMAT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Unknown EXPLAIN format name: '%s'
    </p></li><li class="listitem"><p><a name="error_er_cant_execute_in_read_only_transaction"></a>
      <a class="indexterm" name="idm46734187837200"></a>

      <a class="indexterm" name="idm46734187836160"></a>

      Error number: <code class="literal">1792</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_execute_in_read_only_transaction"><code class="literal">ER_CANT_EXECUTE_IN_READ_ONLY_TRANSACTION</code></a>;
      SQLSTATE: <code class="literal">25006</code>
    </p><p>
      Message: Cannot execute statement in a READ ONLY transaction.
    </p></li><li class="listitem"><p><a name="error_er_too_long_table_partition_comment"></a>
      <a class="indexterm" name="idm46734187829888"></a>

      <a class="indexterm" name="idm46734187828848"></a>

      Error number: <code class="literal">1793</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_too_long_table_partition_comment"><code class="literal">ER_TOO_LONG_TABLE_PARTITION_COMMENT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Comment for table partition '%s' is too long (max = %lu)
    </p></li><li class="listitem"><p><a name="error_er_slave_configuration"></a>
      <a class="indexterm" name="idm46734187822720"></a>

      <a class="indexterm" name="idm46734187821680"></a>

      Error number: <code class="literal">1794</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_configuration"><code class="literal">ER_SLAVE_CONFIGURATION</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Slave is not configured or failed to initialize properly.
      You must at least set --server-id to enable either a master or a
      slave. Additional error messages can be found in the MySQL error
      log.
    </p></li><li class="listitem"><p><a name="error_er_innodb_ft_limit"></a>
      <a class="indexterm" name="idm46734187815536"></a>

      <a class="indexterm" name="idm46734187814496"></a>

      Error number: <code class="literal">1795</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_innodb_ft_limit"><code class="literal">ER_INNODB_FT_LIMIT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: InnoDB presently supports one FULLTEXT index creation at
      a time
    </p></li><li class="listitem"><p><a name="error_er_innodb_no_ft_temp_table"></a>
      <a class="indexterm" name="idm46734187808416"></a>

      <a class="indexterm" name="idm46734187807376"></a>

      Error number: <code class="literal">1796</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_innodb_no_ft_temp_table"><code class="literal">ER_INNODB_NO_FT_TEMP_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot create FULLTEXT index on temporary InnoDB table
    </p></li><li class="listitem"><p><a name="error_er_innodb_ft_wrong_docid_column"></a>
      <a class="indexterm" name="idm46734187801280"></a>

      <a class="indexterm" name="idm46734187800176"></a>

      Error number: <code class="literal">1797</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_innodb_ft_wrong_docid_column"><code class="literal">ER_INNODB_FT_WRONG_DOCID_COLUMN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Column '%s' is of wrong type for an InnoDB FULLTEXT index
    </p></li><li class="listitem"><p><a name="error_er_innodb_ft_wrong_docid_index"></a>
      <a class="indexterm" name="idm46734187794192"></a>

      <a class="indexterm" name="idm46734187793088"></a>

      Error number: <code class="literal">1798</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_innodb_ft_wrong_docid_index"><code class="literal">ER_INNODB_FT_WRONG_DOCID_INDEX</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Index '%s' is of wrong type for an InnoDB FULLTEXT index
    </p></li><li class="listitem"><p><a name="error_er_innodb_online_log_too_big"></a>
      <a class="indexterm" name="idm46734187786976"></a>

      <a class="indexterm" name="idm46734187785936"></a>

      Error number: <code class="literal">1799</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_innodb_online_log_too_big"><code class="literal">ER_INNODB_ONLINE_LOG_TOO_BIG</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Creating index '%s' required more than
      'innodb_online_alter_log_max_size' bytes of modification log.
      Please try again.
    </p></li><li class="listitem"><p><a name="error_er_unknown_alter_algorithm"></a>
      <a class="indexterm" name="idm46734187779712"></a>

      <a class="indexterm" name="idm46734187778672"></a>

      Error number: <code class="literal">1800</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unknown_alter_algorithm"><code class="literal">ER_UNKNOWN_ALTER_ALGORITHM</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Unknown ALGORITHM '%s'
    </p></li><li class="listitem"><p><a name="error_er_unknown_alter_lock"></a>
      <a class="indexterm" name="idm46734187772544"></a>

      <a class="indexterm" name="idm46734187771504"></a>

      Error number: <code class="literal">1801</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unknown_alter_lock"><code class="literal">ER_UNKNOWN_ALTER_LOCK</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Unknown LOCK type '%s'
    </p></li><li class="listitem"><p><a name="error_er_mts_change_master_cant_run_with_gaps"></a>
      <a class="indexterm" name="idm46734187765424"></a>

      <a class="indexterm" name="idm46734187764384"></a>

      Error number: <code class="literal">1802</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_mts_change_master_cant_run_with_gaps"><code class="literal">ER_MTS_CHANGE_MASTER_CANT_RUN_WITH_GAPS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: CHANGE MASTER cannot be executed when the slave was
      stopped with an error or killed in MTS mode. Consider using RESET
      SLAVE or START SLAVE UNTIL.
    </p></li><li class="listitem"><p><a name="error_er_mts_recovery_failure"></a>
      <a class="indexterm" name="idm46734187758160"></a>

      <a class="indexterm" name="idm46734187757120"></a>

      Error number: <code class="literal">1803</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_mts_recovery_failure"><code class="literal">ER_MTS_RECOVERY_FAILURE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Cannot recover after SLAVE errored out in parallel
      execution mode. Additional error messages can be found in the
      MySQL error log.
    </p></li><li class="listitem"><p><a name="error_er_mts_reset_workers"></a>
      <a class="indexterm" name="idm46734187751040"></a>

      <a class="indexterm" name="idm46734187750000"></a>

      Error number: <code class="literal">1804</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_mts_reset_workers"><code class="literal">ER_MTS_RESET_WORKERS</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Cannot clean up worker info tables. Additional error
      messages can be found in the MySQL error log.
    </p></li><li class="listitem"><p><a name="error_er_col_count_doesnt_match_corrupted_v2"></a>
      <a class="indexterm" name="idm46734187743840"></a>

      <a class="indexterm" name="idm46734187742800"></a>

      Error number: <code class="literal">1805</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_col_count_doesnt_match_corrupted_v2"><code class="literal">ER_COL_COUNT_DOESNT_MATCH_CORRUPTED_V2</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Column count of %s.%s is wrong. Expected %d, found %d.
      The table is probably corrupted
    </p></li><li class="listitem"><p><a name="error_er_slave_silent_retry_transaction"></a>
      <a class="indexterm" name="idm46734187736640"></a>

      <a class="indexterm" name="idm46734187735536"></a>

      Error number: <code class="literal">1806</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_silent_retry_transaction"><code class="literal">ER_SLAVE_SILENT_RETRY_TRANSACTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Slave must silently retry current transaction
    </p></li><li class="listitem"><p><a name="error_er_discard_fk_checks_running"></a>
      <a class="indexterm" name="idm46734187729504"></a>

      <a class="indexterm" name="idm46734187728464"></a>

      Error number: <code class="literal">1807</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_discard_fk_checks_running"><code class="literal">ER_DISCARD_FK_CHECKS_RUNNING</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: There is a foreign key check running on table '%s'.
      Cannot discard the table.
    </p></li><li class="listitem"><p><a name="error_er_table_schema_mismatch"></a>
      <a class="indexterm" name="idm46734187722272"></a>

      <a class="indexterm" name="idm46734187721232"></a>

      Error number: <code class="literal">1808</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_schema_mismatch"><code class="literal">ER_TABLE_SCHEMA_MISMATCH</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Schema mismatch (%s)
    </p></li><li class="listitem"><p><a name="error_er_table_in_system_tablespace"></a>
      <a class="indexterm" name="idm46734187715232"></a>

      <a class="indexterm" name="idm46734187714128"></a>

      Error number: <code class="literal">1809</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_in_system_tablespace"><code class="literal">ER_TABLE_IN_SYSTEM_TABLESPACE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Table '%s' in system tablespace
    </p></li><li class="listitem"><p><a name="error_er_io_read_error"></a>
      <a class="indexterm" name="idm46734187708224"></a>

      <a class="indexterm" name="idm46734187707168"></a>

      Error number: <code class="literal">1810</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_io_read_error"><code class="literal">ER_IO_READ_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: IO Read error: (%lu, %s) %s
    </p></li><li class="listitem"><p><a name="error_er_io_write_error"></a>
      <a class="indexterm" name="idm46734187701280"></a>

      <a class="indexterm" name="idm46734187700224"></a>

      Error number: <code class="literal">1811</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_io_write_error"><code class="literal">ER_IO_WRITE_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: IO Write error: (%lu, %s) %s
    </p></li><li class="listitem"><p><a name="error_er_tablespace_missing"></a>
      <a class="indexterm" name="idm46734187694224"></a>

      <a class="indexterm" name="idm46734187693184"></a>

      Error number: <code class="literal">1812</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_tablespace_missing"><code class="literal">ER_TABLESPACE_MISSING</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Tablespace is missing for table %s.
    </p></li><li class="listitem"><p><a name="error_er_tablespace_exists"></a>
      <a class="indexterm" name="idm46734187687136"></a>

      <a class="indexterm" name="idm46734187686096"></a>

      Error number: <code class="literal">1813</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_tablespace_exists"><code class="literal">ER_TABLESPACE_EXISTS</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Tablespace '%s' exists.
    </p></li><li class="listitem"><p><a name="error_er_tablespace_discarded"></a>
      <a class="indexterm" name="idm46734187680128"></a>

      <a class="indexterm" name="idm46734187679088"></a>

      Error number: <code class="literal">1814</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_tablespace_discarded"><code class="literal">ER_TABLESPACE_DISCARDED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Tablespace has been discarded for table '%s'
    </p></li><li class="listitem"><p><a name="error_er_internal_error"></a>
      <a class="indexterm" name="idm46734187673088"></a>

      <a class="indexterm" name="idm46734187672032"></a>

      Error number: <code class="literal">1815</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_internal_error"><code class="literal">ER_INTERNAL_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Internal error: %s
    </p></li><li class="listitem"><p><a name="error_er_innodb_import_error"></a>
      <a class="indexterm" name="idm46734187666048"></a>

      <a class="indexterm" name="idm46734187665008"></a>

      Error number: <code class="literal">1816</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_innodb_import_error"><code class="literal">ER_INNODB_IMPORT_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: ALTER TABLE %s IMPORT TABLESPACE failed with error %lu :
      '%s'
    </p></li><li class="listitem"><p><a name="error_er_innodb_index_corrupt"></a>
      <a class="indexterm" name="idm46734187658928"></a>

      <a class="indexterm" name="idm46734187657888"></a>

      Error number: <code class="literal">1817</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_innodb_index_corrupt"><code class="literal">ER_INNODB_INDEX_CORRUPT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Index corrupt: %s
    </p></li><li class="listitem"><p><a name="error_er_invalid_year_column_length"></a>
      <a class="indexterm" name="idm46734187651856"></a>

      <a class="indexterm" name="idm46734187650752"></a>

      Error number: <code class="literal">1818</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_year_column_length"><code class="literal">ER_INVALID_YEAR_COLUMN_LENGTH</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Supports only YEAR or YEAR(4) column.
    </p></li><li class="listitem"><p><a name="error_er_not_valid_password"></a>
      <a class="indexterm" name="idm46734187644832"></a>

      <a class="indexterm" name="idm46734187643792"></a>

      Error number: <code class="literal">1819</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_not_valid_password"><code class="literal">ER_NOT_VALID_PASSWORD</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Your password does not satisfy the current policy
      requirements
    </p></li><li class="listitem"><p><a name="error_er_must_change_password"></a>
      <a class="indexterm" name="idm46734187637888"></a>

      <a class="indexterm" name="idm46734187636848"></a>

      Error number: <code class="literal">1820</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_must_change_password"><code class="literal">ER_MUST_CHANGE_PASSWORD</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: You must reset your password using ALTER USER statement
      before executing this statement.
    </p></li><li class="listitem"><p><a name="error_er_fk_no_index_child"></a>
      <a class="indexterm" name="idm46734187630816"></a>

      <a class="indexterm" name="idm46734187629776"></a>

      Error number: <code class="literal">1821</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fk_no_index_child"><code class="literal">ER_FK_NO_INDEX_CHILD</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Failed to add the foreign key constaint. Missing index
      for constraint '%s' in the foreign table '%s'
    </p></li><li class="listitem"><p><a name="error_er_fk_no_index_parent"></a>
      <a class="indexterm" name="idm46734187623728"></a>

      <a class="indexterm" name="idm46734187622688"></a>

      Error number: <code class="literal">1822</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fk_no_index_parent"><code class="literal">ER_FK_NO_INDEX_PARENT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Failed to add the foreign key constaint. Missing index
      for constraint '%s' in the referenced table '%s'
    </p></li><li class="listitem"><p><a name="error_er_fk_fail_add_system"></a>
      <a class="indexterm" name="idm46734187616640"></a>

      <a class="indexterm" name="idm46734187615600"></a>

      Error number: <code class="literal">1823</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fk_fail_add_system"><code class="literal">ER_FK_FAIL_ADD_SYSTEM</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Failed to add the foreign key constraint '%s' to system
      tables
    </p></li><li class="listitem"><p><a name="error_er_fk_cannot_open_parent"></a>
      <a class="indexterm" name="idm46734187609584"></a>

      <a class="indexterm" name="idm46734187608544"></a>

      Error number: <code class="literal">1824</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fk_cannot_open_parent"><code class="literal">ER_FK_CANNOT_OPEN_PARENT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Failed to open the referenced table '%s'
    </p></li><li class="listitem"><p><a name="error_er_fk_incorrect_option"></a>
      <a class="indexterm" name="idm46734187602400"></a>

      <a class="indexterm" name="idm46734187601360"></a>

      Error number: <code class="literal">1825</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fk_incorrect_option"><code class="literal">ER_FK_INCORRECT_OPTION</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Failed to add the foreign key constraint on table '%s'.
      Incorrect options in FOREIGN KEY constraint '%s'
    </p></li><li class="listitem"><p><a name="error_er_fk_dup_name"></a>
      <a class="indexterm" name="idm46734187595296"></a>

      <a class="indexterm" name="idm46734187594240"></a>

      Error number: <code class="literal">1826</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fk_dup_name"><code class="literal">ER_FK_DUP_NAME</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Duplicate foreign key constraint name '%s'
    </p></li><li class="listitem"><p><a name="error_er_password_format"></a>
      <a class="indexterm" name="idm46734187588224"></a>

      <a class="indexterm" name="idm46734187587184"></a>

      Error number: <code class="literal">1827</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_password_format"><code class="literal">ER_PASSWORD_FORMAT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The password hash doesn't have the expected format. Check
      if the correct password algorithm is being used with the
      PASSWORD() function.
    </p></li><li class="listitem"><p><a name="error_er_fk_column_cannot_drop"></a>
      <a class="indexterm" name="idm46734187581024"></a>

      <a class="indexterm" name="idm46734187579984"></a>

      Error number: <code class="literal">1828</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fk_column_cannot_drop"><code class="literal">ER_FK_COLUMN_CANNOT_DROP</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot drop column '%s': needed in a foreign key
      constraint '%s'
    </p></li><li class="listitem"><p><a name="error_er_fk_column_cannot_drop_child"></a>
      <a class="indexterm" name="idm46734187573936"></a>

      <a class="indexterm" name="idm46734187572832"></a>

      Error number: <code class="literal">1829</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fk_column_cannot_drop_child"><code class="literal">ER_FK_COLUMN_CANNOT_DROP_CHILD</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot drop column '%s': needed in a foreign key
      constraint '%s' of table '%s'
    </p></li><li class="listitem"><p><a name="error_er_fk_column_not_null"></a>
      <a class="indexterm" name="idm46734187566752"></a>

      <a class="indexterm" name="idm46734187565712"></a>

      Error number: <code class="literal">1830</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fk_column_not_null"><code class="literal">ER_FK_COLUMN_NOT_NULL</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Column '%s' cannot be NOT NULL: needed in a foreign key
      constraint '%s' SET NULL
    </p></li><li class="listitem"><p><a name="error_er_dup_index"></a>
      <a class="indexterm" name="idm46734187559664"></a>

      <a class="indexterm" name="idm46734187558624"></a>

      Error number: <code class="literal">1831</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_dup_index"><code class="literal">ER_DUP_INDEX</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Duplicate index '%s' defined on the table '%s.%s'. This
      is deprecated and will be disallowed in a future release.
    </p></li><li class="listitem"><p><a name="error_er_fk_column_cannot_change"></a>
      <a class="indexterm" name="idm46734187552592"></a>

      <a class="indexterm" name="idm46734187551552"></a>

      Error number: <code class="literal">1832</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fk_column_cannot_change"><code class="literal">ER_FK_COLUMN_CANNOT_CHANGE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot change column '%s': used in a foreign key
      constraint '%s'
    </p></li><li class="listitem"><p><a name="error_er_fk_column_cannot_change_child"></a>
      <a class="indexterm" name="idm46734187545504"></a>

      <a class="indexterm" name="idm46734187544400"></a>

      Error number: <code class="literal">1833</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fk_column_cannot_change_child"><code class="literal">ER_FK_COLUMN_CANNOT_CHANGE_CHILD</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot change column '%s': used in a foreign key
      constraint '%s' of table '%s'
    </p></li><li class="listitem"><p><a name="error_er_fk_cannot_delete_parent"></a>
      <a class="indexterm" name="idm46734187538384"></a>

      <a class="indexterm" name="idm46734187537344"></a>

      Error number: <code class="literal">1834</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fk_cannot_delete_parent"><code class="literal">ER_FK_CANNOT_DELETE_PARENT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot delete rows from table which is parent in a
      foreign key constraint '%s' of table '%s'
    </p><p>
      <a class="link" href="error-handling.html#error_er_fk_cannot_delete_parent"><code class="literal">ER_FK_CANNOT_DELETE_PARENT</code></a> was
      removed after 5.7.3.
    </p></li><li class="listitem"><p><a name="error_er_unused5"></a>
      <a class="indexterm" name="idm46734187529584"></a>

      <a class="indexterm" name="idm46734187528544"></a>

      Error number: <code class="literal">1834</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unused5"><code class="literal">ER_UNUSED5</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Cannot delete rows from table which is parent in a
      foreign key constraint '%s' of table '%s'
    </p><p>
      <a class="link" href="error-handling.html#error_er_unused5"><code class="literal">ER_UNUSED5</code></a> was added in 5.7.4.
    </p></li><li class="listitem"><p><a name="error_er_malformed_packet"></a>
      <a class="indexterm" name="idm46734187520848"></a>

      <a class="indexterm" name="idm46734187519808"></a>

      Error number: <code class="literal">1835</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_malformed_packet"><code class="literal">ER_MALFORMED_PACKET</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Malformed communication packet.
    </p></li><li class="listitem"><p><a name="error_er_read_only_mode"></a>
      <a class="indexterm" name="idm46734187513824"></a>

      <a class="indexterm" name="idm46734187512768"></a>

      Error number: <code class="literal">1836</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_read_only_mode"><code class="literal">ER_READ_ONLY_MODE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Running in read-only mode
    </p></li><li class="listitem"><p><a name="error_er_gtid_next_type_undefined_group"></a>
      <a class="indexterm" name="idm46734187506768"></a>

      <a class="indexterm" name="idm46734187505664"></a>

      Error number: <code class="literal">1837</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gtid_next_type_undefined_group"><code class="literal">ER_GTID_NEXT_TYPE_UNDEFINED_GROUP</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: When @@SESSION.GTID_NEXT is set to a GTID, you must
      explicitly set it to a different value after a COMMIT or ROLLBACK.
      Please check GTID_NEXT variable manual page for detailed
      explanation. Current @@SESSION.GTID_NEXT is '%s'.
    </p></li><li class="listitem"><p><a name="error_er_variable_not_settable_in_sp"></a>
      <a class="indexterm" name="idm46734187499488"></a>

      <a class="indexterm" name="idm46734187498384"></a>

      Error number: <code class="literal">1838</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_variable_not_settable_in_sp"><code class="literal">ER_VARIABLE_NOT_SETTABLE_IN_SP</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The system variable %s cannot be set in stored
      procedures.
    </p></li><li class="listitem"><p><a name="error_er_cant_set_gtid_purged_when_gtid_mode_is_off"></a>
      <a class="indexterm" name="idm46734187492352"></a>

      <a class="indexterm" name="idm46734187491232"></a>

      Error number: <code class="literal">1839</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_set_gtid_purged_when_gtid_mode_is_off"><code class="literal">ER_CANT_SET_GTID_PURGED_WHEN_GTID_MODE_IS_OFF</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: @@GLOBAL.GTID_PURGED can only be set when
      @@GLOBAL.GTID_MODE = ON.
    </p></li><li class="listitem"><p><a name="error_er_cant_set_gtid_purged_when_gtid_executed_is_not_empty"></a>
      <a class="indexterm" name="idm46734187485024"></a>

      <a class="indexterm" name="idm46734187483984"></a>

      Error number: <code class="literal">1840</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_set_gtid_purged_when_gtid_executed_is_not_empty"><code class="literal">ER_CANT_SET_GTID_PURGED_WHEN_GTID_EXECUTED_IS_NOT_EMPTY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: @@GLOBAL.GTID_PURGED can only be set when
      @@GLOBAL.GTID_EXECUTED is empty.
    </p></li><li class="listitem"><p><a name="error_er_cant_set_gtid_purged_when_owned_gtids_is_not_empty"></a>
      <a class="indexterm" name="idm46734187477616"></a>

      <a class="indexterm" name="idm46734187476576"></a>

      Error number: <code class="literal">1841</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_set_gtid_purged_when_owned_gtids_is_not_empty"><code class="literal">ER_CANT_SET_GTID_PURGED_WHEN_OWNED_GTIDS_IS_NOT_EMPTY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: @@GLOBAL.GTID_PURGED can only be set when there are no
      ongoing transactions (not even in other clients).
    </p></li><li class="listitem"><p><a name="error_er_gtid_purged_was_changed"></a>
      <a class="indexterm" name="idm46734187470320"></a>

      <a class="indexterm" name="idm46734187469280"></a>

      Error number: <code class="literal">1842</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gtid_purged_was_changed"><code class="literal">ER_GTID_PURGED_WAS_CHANGED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: @@GLOBAL.GTID_PURGED was changed from '%s' to '%s'.
    </p></li><li class="listitem"><p><a name="error_er_gtid_executed_was_changed"></a>
      <a class="indexterm" name="idm46734187463248"></a>

      <a class="indexterm" name="idm46734187462208"></a>

      Error number: <code class="literal">1843</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gtid_executed_was_changed"><code class="literal">ER_GTID_EXECUTED_WAS_CHANGED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: @@GLOBAL.GTID_EXECUTED was changed from '%s' to '%s'.
    </p></li><li class="listitem"><p><a name="error_er_binlog_stmt_mode_and_no_repl_tables"></a>
      <a class="indexterm" name="idm46734187456064"></a>

      <a class="indexterm" name="idm46734187455024"></a>

      Error number: <code class="literal">1844</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_stmt_mode_and_no_repl_tables"><code class="literal">ER_BINLOG_STMT_MODE_AND_NO_REPL_TABLES</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot execute statement: impossible to write to binary
      log since BINLOG_FORMAT = STATEMENT, and both replicated and non
      replicated tables are written to.
    </p></li><li class="listitem"><p><a name="error_er_alter_operation_not_supported"></a>
      <a class="indexterm" name="idm46734187448784"></a>

      <a class="indexterm" name="idm46734187447680"></a>

      Error number: <code class="literal">1845</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED</code></a>;
      SQLSTATE: <code class="literal">0A000</code>
    </p><p>
      Message: %s is not supported for this operation. Try %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED</code></a>
      was added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_alter_operation_not_supported_reason"></a>
      <a class="indexterm" name="idm46734187440064"></a>

      <a class="indexterm" name="idm46734187439024"></a>

      Error number: <code class="literal">1846</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON</code></a>;
      SQLSTATE: <code class="literal">0A000</code>
    </p><p>
      Message: %s is not supported. Reason: %s. Try %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON</code></a>
      was added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_alter_operation_not_supported_reason_copy"></a>
      <a class="indexterm" name="idm46734187431216"></a>

      <a class="indexterm" name="idm46734187430176"></a>

      Error number: <code class="literal">1847</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_copy"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COPY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: COPY algorithm requires a lock
    </p><p>
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_copy"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COPY</code></a>
      was added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_alter_operation_not_supported_reason_partition"></a>
      <a class="indexterm" name="idm46734187422208"></a>

      <a class="indexterm" name="idm46734187421088"></a>

      Error number: <code class="literal">1848</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_partition"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_PARTITION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Partition specific operations do not yet support
      LOCK/ALGORITHM
    </p><p>
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_partition"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_PARTITION</code></a>
      was added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_alter_operation_not_supported_reason_fk_rename"></a>
      <a class="indexterm" name="idm46734187413200"></a>

      <a class="indexterm" name="idm46734187412080"></a>

      Error number: <code class="literal">1849</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_fk_rename"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_RENAME</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Columns participating in a foreign key are renamed
    </p><p>
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_fk_rename"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_RENAME</code></a>
      was added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_alter_operation_not_supported_reason_column_type"></a>
      <a class="indexterm" name="idm46734187404176"></a>

      <a class="indexterm" name="idm46734187403136"></a>

      Error number: <code class="literal">1850</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_column_type"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COLUMN_TYPE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot change column type INPLACE
    </p><p>
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_column_type"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_COLUMN_TYPE</code></a>
      was added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_alter_operation_not_supported_reason_fk_check"></a>
      <a class="indexterm" name="idm46734187395152"></a>

      <a class="indexterm" name="idm46734187394112"></a>

      Error number: <code class="literal">1851</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_fk_check"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_CHECK</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Adding foreign keys needs foreign_key_checks=OFF
    </p><p>
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_fk_check"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FK_CHECK</code></a>
      was added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_alter_operation_not_supported_reason_ignore"></a>
      <a class="indexterm" name="idm46734187386256"></a>

      <a class="indexterm" name="idm46734187385136"></a>

      Error number: <code class="literal">1852</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_ignore"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_IGNORE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Creating unique indexes with IGNORE requires COPY
      algorithm to remove duplicate rows
    </p><p>
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_ignore"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_IGNORE</code></a>
      was added in 5.7.1, removed after 5.7.3.
    </p></li><li class="listitem"><p><a name="error_er_unused6"></a>
      <a class="indexterm" name="idm46734187377376"></a>

      <a class="indexterm" name="idm46734187376336"></a>

      Error number: <code class="literal">1852</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unused6"><code class="literal">ER_UNUSED6</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Creating unique indexes with IGNORE requires COPY
      algorithm to remove duplicate rows
    </p><p>
      <a class="link" href="error-handling.html#error_er_unused6"><code class="literal">ER_UNUSED6</code></a> was added in 5.7.4.
    </p></li><li class="listitem"><p><a name="error_er_alter_operation_not_supported_reason_nopk"></a>
      <a class="indexterm" name="idm46734187368592"></a>

      <a class="indexterm" name="idm46734187367552"></a>

      Error number: <code class="literal">1853</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_nopk"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_NOPK</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Dropping a primary key is not allowed without also adding
      a new primary key
    </p><p>
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_nopk"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_NOPK</code></a>
      was added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_alter_operation_not_supported_reason_autoinc"></a>
      <a class="indexterm" name="idm46734187359600"></a>

      <a class="indexterm" name="idm46734187358480"></a>

      Error number: <code class="literal">1854</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_autoinc"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_AUTOINC</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Adding an auto-increment column requires a lock
    </p><p>
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_autoinc"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_AUTOINC</code></a>
      was added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_alter_operation_not_supported_reason_hidden_fts"></a>
      <a class="indexterm" name="idm46734187350576"></a>

      <a class="indexterm" name="idm46734187349536"></a>

      Error number: <code class="literal">1855</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_hidden_fts"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_HIDDEN_FTS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot replace hidden FTS_DOC_ID with a user-visible one
    </p><p>
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_hidden_fts"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_HIDDEN_FTS</code></a>
      was added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_alter_operation_not_supported_reason_change_fts"></a>
      <a class="indexterm" name="idm46734187341424"></a>

      <a class="indexterm" name="idm46734187340384"></a>

      Error number: <code class="literal">1856</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_change_fts"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_CHANGE_FTS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot drop or rename FTS_DOC_ID
    </p><p>
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_change_fts"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_CHANGE_FTS</code></a>
      was added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_alter_operation_not_supported_reason_fts"></a>
      <a class="indexterm" name="idm46734187332400"></a>

      <a class="indexterm" name="idm46734187331360"></a>

      Error number: <code class="literal">1857</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_fts"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FTS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Fulltext index creation requires a lock
    </p><p>
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_fts"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_FTS</code></a>
      was added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_sql_slave_skip_counter_not_settable_in_gtid_mode"></a>
      <a class="indexterm" name="idm46734187323408"></a>

      <a class="indexterm" name="idm46734187322368"></a>

      Error number: <code class="literal">1858</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sql_slave_skip_counter_not_settable_in_gtid_mode"><code class="literal">ER_SQL_SLAVE_SKIP_COUNTER_NOT_SETTABLE_IN_GTID_MODE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: sql_slave_skip_counter can not be set when the server is
      running with @@GLOBAL.GTID_MODE = ON. Instead, for each
      transaction that you want to skip, generate an empty transaction
      with the same GTID as the transaction
    </p><p>
      <a class="link" href="error-handling.html#error_er_sql_slave_skip_counter_not_settable_in_gtid_mode"><code class="literal">ER_SQL_SLAVE_SKIP_COUNTER_NOT_SETTABLE_IN_GTID_MODE</code></a>
      was added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_dup_unknown_in_index"></a>
      <a class="indexterm" name="idm46734187314224"></a>

      <a class="indexterm" name="idm46734187313184"></a>

      Error number: <code class="literal">1859</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_dup_unknown_in_index"><code class="literal">ER_DUP_UNKNOWN_IN_INDEX</code></a>; SQLSTATE:
      <code class="literal">23000</code>
    </p><p>
      Message: Duplicate entry for key '%s'
    </p><p>
      <a class="link" href="error-handling.html#error_er_dup_unknown_in_index"><code class="literal">ER_DUP_UNKNOWN_IN_INDEX</code></a> was added
      in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_ident_causes_too_long_path"></a>
      <a class="indexterm" name="idm46734187305552"></a>

      <a class="indexterm" name="idm46734187304448"></a>

      Error number: <code class="literal">1860</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_ident_causes_too_long_path"><code class="literal">ER_IDENT_CAUSES_TOO_LONG_PATH</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Long database name and identifier for object resulted in
      path length exceeding %d characters. Path: '%s'.
    </p><p>
      <a class="link" href="error-handling.html#error_er_ident_causes_too_long_path"><code class="literal">ER_IDENT_CAUSES_TOO_LONG_PATH</code></a> was
      added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_alter_operation_not_supported_reason_not_null"></a>
      <a class="indexterm" name="idm46734187296624"></a>

      <a class="indexterm" name="idm46734187295584"></a>

      Error number: <code class="literal">1861</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_not_null"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_NOT_NULL</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: cannot silently convert NULL values, as required in this
      SQL_MODE
    </p><p>
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_not_null"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_NOT_NULL</code></a>
      was added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_must_change_password_login"></a>
      <a class="indexterm" name="idm46734187287792"></a>

      <a class="indexterm" name="idm46734187286688"></a>

      Error number: <code class="literal">1862</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_must_change_password_login"><code class="literal">ER_MUST_CHANGE_PASSWORD_LOGIN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Your password has expired. To log in you must change it
      using a client that supports expired passwords.
    </p><p>
      <a class="link" href="error-handling.html#error_er_must_change_password_login"><code class="literal">ER_MUST_CHANGE_PASSWORD_LOGIN</code></a> was
      added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_row_in_wrong_partition"></a>
      <a class="indexterm" name="idm46734187278976"></a>

      <a class="indexterm" name="idm46734187277936"></a>

      Error number: <code class="literal">1863</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_row_in_wrong_partition"><code class="literal">ER_ROW_IN_WRONG_PARTITION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Found a row in wrong partition %s
    </p><p>
      <a class="link" href="error-handling.html#error_er_row_in_wrong_partition"><code class="literal">ER_ROW_IN_WRONG_PARTITION</code></a> was
      added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_mts_event_bigger_pending_jobs_size_max"></a>
      <a class="indexterm" name="idm46734187270080"></a>

      <a class="indexterm" name="idm46734187269040"></a>

      Error number: <code class="literal">1864</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_mts_event_bigger_pending_jobs_size_max"><code class="literal">ER_MTS_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot schedule event %s, relay-log name %s, position %s
      to Worker thread because its size %lu exceeds %lu of
      slave_pending_jobs_size_max.
    </p><p>
      <a class="link" href="error-handling.html#error_er_mts_event_bigger_pending_jobs_size_max"><code class="literal">ER_MTS_EVENT_BIGGER_PENDING_JOBS_SIZE_MAX</code></a>
      was added in 5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_innodb_no_ft_uses_parser"></a>
      <a class="indexterm" name="idm46734187260992"></a>

      <a class="indexterm" name="idm46734187259952"></a>

      Error number: <code class="literal">1865</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_innodb_no_ft_uses_parser"><code class="literal">ER_INNODB_NO_FT_USES_PARSER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot CREATE FULLTEXT INDEX WITH PARSER on InnoDB table
    </p><p>
      <a class="link" href="error-handling.html#error_er_innodb_no_ft_uses_parser"><code class="literal">ER_INNODB_NO_FT_USES_PARSER</code></a> was
      added in 5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_binlog_logical_corruption"></a>
      <a class="indexterm" name="idm46734187252176"></a>

      <a class="indexterm" name="idm46734187251136"></a>

      Error number: <code class="literal">1866</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_logical_corruption"><code class="literal">ER_BINLOG_LOGICAL_CORRUPTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The binary log file '%s' is logically corrupted: %s
    </p><p>
      <a class="link" href="error-handling.html#error_er_binlog_logical_corruption"><code class="literal">ER_BINLOG_LOGICAL_CORRUPTION</code></a> was
      added in 5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_warn_purge_log_in_use"></a>
      <a class="indexterm" name="idm46734187243296"></a>

      <a class="indexterm" name="idm46734187242256"></a>

      Error number: <code class="literal">1867</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_purge_log_in_use"><code class="literal">ER_WARN_PURGE_LOG_IN_USE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: file %s was not purged because it was being read by %d
      thread(s), purged only %d out of %d files.
    </p><p>
      <a class="link" href="error-handling.html#error_er_warn_purge_log_in_use"><code class="literal">ER_WARN_PURGE_LOG_IN_USE</code></a> was added
      in 5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_warn_purge_log_is_active"></a>
      <a class="indexterm" name="idm46734187234544"></a>

      <a class="indexterm" name="idm46734187233504"></a>

      Error number: <code class="literal">1868</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_purge_log_is_active"><code class="literal">ER_WARN_PURGE_LOG_IS_ACTIVE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: file %s was not purged because it is the active log file.
    </p><p>
      <a class="link" href="error-handling.html#error_er_warn_purge_log_is_active"><code class="literal">ER_WARN_PURGE_LOG_IS_ACTIVE</code></a> was
      added in 5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_auto_increment_conflict"></a>
      <a class="indexterm" name="idm46734187225776"></a>

      <a class="indexterm" name="idm46734187224736"></a>

      Error number: <code class="literal">1869</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_auto_increment_conflict"><code class="literal">ER_AUTO_INCREMENT_CONFLICT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Auto-increment value in UPDATE conflicts with internally
      generated values
    </p><p>
      <a class="link" href="error-handling.html#error_er_auto_increment_conflict"><code class="literal">ER_AUTO_INCREMENT_CONFLICT</code></a> was
      added in 5.7.2.
    </p></li><li class="listitem"><p><a name="error_warn_on_blockhole_in_rbr"></a>
      <a class="indexterm" name="idm46734187217072"></a>

      <a class="indexterm" name="idm46734187216032"></a>

      Error number: <code class="literal">1870</code>; Symbol:
      <a class="link" href="error-handling.html#error_warn_on_blockhole_in_rbr"><code class="literal">WARN_ON_BLOCKHOLE_IN_RBR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Row events are not logged for %s statements that modify
      BLACKHOLE tables in row format. Table(s): '%s'
    </p><p>
      <a class="link" href="error-handling.html#error_warn_on_blockhole_in_rbr"><code class="literal">WARN_ON_BLOCKHOLE_IN_RBR</code></a> was added
      in 5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_slave_mi_init_repository"></a>
      <a class="indexterm" name="idm46734187208208"></a>

      <a class="indexterm" name="idm46734187207168"></a>

      Error number: <code class="literal">1871</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_mi_init_repository"><code class="literal">ER_SLAVE_MI_INIT_REPOSITORY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Slave failed to initialize master info structure from the
      repository
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_mi_init_repository"><code class="literal">ER_SLAVE_MI_INIT_REPOSITORY</code></a> was
      added in 5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_slave_rli_init_repository"></a>
      <a class="indexterm" name="idm46734187199376"></a>

      <a class="indexterm" name="idm46734187198336"></a>

      Error number: <code class="literal">1872</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_rli_init_repository"><code class="literal">ER_SLAVE_RLI_INIT_REPOSITORY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Slave failed to initialize relay log info structure from
      the repository
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_rli_init_repository"><code class="literal">ER_SLAVE_RLI_INIT_REPOSITORY</code></a> was
      added in 5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_access_denied_change_user_error"></a>
      <a class="indexterm" name="idm46734187190496"></a>

      <a class="indexterm" name="idm46734187189456"></a>

      Error number: <code class="literal">1873</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_access_denied_change_user_error"><code class="literal">ER_ACCESS_DENIED_CHANGE_USER_ERROR</code></a>;
      SQLSTATE: <code class="literal">28000</code>
    </p><p>
      Message: Access denied trying to change to user '%s'@'%s' (using
      password: %s). Disconnecting.
    </p><p>
      <a class="link" href="error-handling.html#error_er_access_denied_change_user_error"><code class="literal">ER_ACCESS_DENIED_CHANGE_USER_ERROR</code></a>
      was added in 5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_innodb_read_only"></a>
      <a class="indexterm" name="idm46734187181584"></a>

      <a class="indexterm" name="idm46734187180544"></a>

      Error number: <code class="literal">1874</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_innodb_read_only"><code class="literal">ER_INNODB_READ_ONLY</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: InnoDB is in read only mode.
    </p><p>
      <a class="link" href="error-handling.html#error_er_innodb_read_only"><code class="literal">ER_INNODB_READ_ONLY</code></a> was added in
      5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_stop_slave_sql_thread_timeout"></a>
      <a class="indexterm" name="idm46734187172848"></a>

      <a class="indexterm" name="idm46734187171744"></a>

      Error number: <code class="literal">1875</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_stop_slave_sql_thread_timeout"><code class="literal">ER_STOP_SLAVE_SQL_THREAD_TIMEOUT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: STOP SLAVE command execution is incomplete: Slave SQL
      thread got the stop signal, thread is busy, SQL thread will stop
      once the current task is complete.
    </p><p>
      <a class="link" href="error-handling.html#error_er_stop_slave_sql_thread_timeout"><code class="literal">ER_STOP_SLAVE_SQL_THREAD_TIMEOUT</code></a>
      was added in 5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_stop_slave_io_thread_timeout"></a>
      <a class="indexterm" name="idm46734187163968"></a>

      <a class="indexterm" name="idm46734187162864"></a>

      Error number: <code class="literal">1876</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_stop_slave_io_thread_timeout"><code class="literal">ER_STOP_SLAVE_IO_THREAD_TIMEOUT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: STOP SLAVE command execution is incomplete: Slave IO
      thread got the stop signal, thread is busy, IO thread will stop
      once the current task is complete.
    </p><p>
      <a class="link" href="error-handling.html#error_er_stop_slave_io_thread_timeout"><code class="literal">ER_STOP_SLAVE_IO_THREAD_TIMEOUT</code></a>
      was added in 5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_table_corrupt"></a>
      <a class="indexterm" name="idm46734187155136"></a>

      <a class="indexterm" name="idm46734187154080"></a>

      Error number: <code class="literal">1877</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_corrupt"><code class="literal">ER_TABLE_CORRUPT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Operation cannot be performed. The table '%s.%s' is
      missing, corrupt or contains bad data.
    </p><p>
      <a class="link" href="error-handling.html#error_er_table_corrupt"><code class="literal">ER_TABLE_CORRUPT</code></a> was added in
      5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_temp_file_write_failure"></a>
      <a class="indexterm" name="idm46734187146448"></a>

      <a class="indexterm" name="idm46734187145408"></a>

      Error number: <code class="literal">1878</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_temp_file_write_failure"><code class="literal">ER_TEMP_FILE_WRITE_FAILURE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Temporary file write failure.
    </p><p>
      <a class="link" href="error-handling.html#error_er_temp_file_write_failure"><code class="literal">ER_TEMP_FILE_WRITE_FAILURE</code></a> was
      added in 5.7.3.
    </p></li><li class="listitem"><p><a name="error_er_innodb_ft_aux_not_hex_id"></a>
      <a class="indexterm" name="idm46734187137600"></a>

      <a class="indexterm" name="idm46734187136560"></a>

      Error number: <code class="literal">1879</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_innodb_ft_aux_not_hex_id"><code class="literal">ER_INNODB_FT_AUX_NOT_HEX_ID</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Upgrade index name failed, please use create index(alter
      table) algorithm copy to rebuild index.
    </p><p>
      <a class="link" href="error-handling.html#error_er_innodb_ft_aux_not_hex_id"><code class="literal">ER_INNODB_FT_AUX_NOT_HEX_ID</code></a> was
      added in 5.7.4.
    </p></li><li class="listitem"><p><a name="error_er_old_temporals_upgraded"></a>
      <a class="indexterm" name="idm46734187128736"></a>

      <a class="indexterm" name="idm46734187127696"></a>

      Error number: <code class="literal">1880</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_old_temporals_upgraded"><code class="literal">ER_OLD_TEMPORALS_UPGRADED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: TIME/TIMESTAMP/DATETIME columns of old format have been
      upgraded to the new format.
    </p><p>
      <a class="link" href="error-handling.html#error_er_old_temporals_upgraded"><code class="literal">ER_OLD_TEMPORALS_UPGRADED</code></a> was
      added in 5.7.4.
    </p></li><li class="listitem"><p><a name="error_er_innodb_forced_recovery"></a>
      <a class="indexterm" name="idm46734187119888"></a>

      <a class="indexterm" name="idm46734187118848"></a>

      Error number: <code class="literal">1881</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_innodb_forced_recovery"><code class="literal">ER_INNODB_FORCED_RECOVERY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Operation not allowed when innodb_forced_recovery &gt; 0.
    </p><p>
      <a class="link" href="error-handling.html#error_er_innodb_forced_recovery"><code class="literal">ER_INNODB_FORCED_RECOVERY</code></a> was
      added in 5.7.4.
    </p></li><li class="listitem"><p><a name="error_er_aes_invalid_iv"></a>
      <a class="indexterm" name="idm46734187111136"></a>

      <a class="indexterm" name="idm46734187110080"></a>

      Error number: <code class="literal">1882</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_aes_invalid_iv"><code class="literal">ER_AES_INVALID_IV</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The initialization vector supplied to %s is too short.
      Must be at least %d bytes long
    </p><p>
      <a class="link" href="error-handling.html#error_er_aes_invalid_iv"><code class="literal">ER_AES_INVALID_IV</code></a> was added in
      5.7.4.
    </p></li><li class="listitem"><p><a name="error_er_plugin_cannot_be_uninstalled"></a>
      <a class="indexterm" name="idm46734187102384"></a>

      <a class="indexterm" name="idm46734187101280"></a>

      Error number: <code class="literal">1883</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_plugin_cannot_be_uninstalled"><code class="literal">ER_PLUGIN_CANNOT_BE_UNINSTALLED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Plugin '%s' cannot be uninstalled now. %s
    </p><p>
      <a class="link" href="error-handling.html#error_er_plugin_cannot_be_uninstalled"><code class="literal">ER_PLUGIN_CANNOT_BE_UNINSTALLED</code></a>
      was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_gtid_unsafe_binlog_splittable_statement_and_gtid_group"></a>
      <a class="indexterm" name="idm46734187093472"></a>

      <a class="indexterm" name="idm46734187092432"></a>

      Error number: <code class="literal">1884</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gtid_unsafe_binlog_splittable_statement_and_gtid_group"><code class="literal">ER_GTID_UNSAFE_BINLOG_SPLITTABLE_STATEMENT_AND_GTID_GROUP</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot execute statement because it needs to be written
      to the binary log as multiple statements, and this is not allowed
      when @@SESSION.GTID_NEXT == 'UUID:NUMBER'.
    </p><p>
      <a class="link" href="error-handling.html#error_er_gtid_unsafe_binlog_splittable_statement_and_gtid_group"><code class="literal">ER_GTID_UNSAFE_BINLOG_SPLITTABLE_STATEMENT_AND_GTID_GROUP</code></a>
      was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_slave_has_more_gtids_than_master"></a>
      <a class="indexterm" name="idm46734187084208"></a>

      <a class="indexterm" name="idm46734187083168"></a>

      Error number: <code class="literal">1885</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_has_more_gtids_than_master"><code class="literal">ER_SLAVE_HAS_MORE_GTIDS_THAN_MASTER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Slave has more GTIDs than the master has, using the
      master's SERVER_UUID. This may indicate that the end of the binary
      log was truncated or that the last binary log file was lost, e.g.,
      after a power or disk failure when sync_binlog != 1. The master
      may or may not have rolled back transactions that were already
      replicated to the slave. Suggest to replicate any transactions
      that master has rolled back from slave to master, and/or commit
      empty transactions on master to account for transactions that have
      been committed on master but are not included in GTID_EXECUTED.
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_has_more_gtids_than_master"><code class="literal">ER_SLAVE_HAS_MORE_GTIDS_THAN_MASTER</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_missing_key"></a>
      <a class="indexterm" name="idm46734187074816"></a>

      <a class="indexterm" name="idm46734187073760"></a>

      Error number: <code class="literal">1886</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_missing_key"><code class="literal">ER_MISSING_KEY</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The table '%s.%s' does not have the necessary key(s)
      defined on it. Please check the table definition and create
      index(s) accordingly.
    </p><p>
      <a class="link" href="error-handling.html#error_er_missing_key"><code class="literal">ER_MISSING_KEY</code></a> was added in
      5.7.22.
    </p></li><li class="listitem"><p><a name="error_warn_named_pipe_access_everyone"></a>
      <a class="indexterm" name="idm46734187065952"></a>

      <a class="indexterm" name="idm46734187064848"></a>

      Error number: <code class="literal">1887</code>; Symbol:
      <a class="link" href="error-handling.html#error_warn_named_pipe_access_everyone"><code class="literal">WARN_NAMED_PIPE_ACCESS_EVERYONE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Setting named_pipe_full_access_group='%s' is insecure.
      Consider using a Windows group with fewer members.
    </p><p>
      <a class="link" href="error-handling.html#error_warn_named_pipe_access_everyone"><code class="literal">WARN_NAMED_PIPE_ACCESS_EVERYONE</code></a>
      was added in 5.7.27.
    </p></li><li class="listitem"><p><a name="error_er_found_missing_gtids"></a>
      <a class="indexterm" name="idm46734187057136"></a>

      <a class="indexterm" name="idm46734187056096"></a>

      Error number: <code class="literal">1888</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_found_missing_gtids"><code class="literal">ER_FOUND_MISSING_GTIDS</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Cannot replicate to server with server_uuid='%s' because
      the present server has purged required binary logs. The connecting
      server needs to replicate the missing transactions from elsewhere,
      or be replaced by a new server created from a more recent backup.
      To prevent this error in the future, consider increasing the
      binary log expiration period on the present server. %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_found_missing_gtids"><code class="literal">ER_FOUND_MISSING_GTIDS</code></a> was added
      in 5.7.29.
    </p></li><li class="listitem"><p><a name="error_er_slave_io_thread_must_stop"></a>
      <a class="indexterm" name="idm46734187048016"></a>

      <a class="indexterm" name="idm46734187046976"></a>

      Error number: <code class="literal">1906</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_io_thread_must_stop"><code class="literal">ER_SLAVE_IO_THREAD_MUST_STOP</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: This operation cannot be performed with a running slave
      io thread; run STOP SLAVE IO_THREAD first.
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_io_thread_must_stop"><code class="literal">ER_SLAVE_IO_THREAD_MUST_STOP</code></a> was
      added in 5.7.4, removed after 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_file_corrupt"></a>
      <a class="indexterm" name="idm46734187039248"></a>

      <a class="indexterm" name="idm46734187038192"></a>

      Error number: <code class="literal">3000</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_file_corrupt"><code class="literal">ER_FILE_CORRUPT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: File %s is corrupted
    </p></li><li class="listitem"><p><a name="error_er_error_on_master"></a>
      <a class="indexterm" name="idm46734187032192"></a>

      <a class="indexterm" name="idm46734187031152"></a>

      Error number: <code class="literal">3001</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_error_on_master"><code class="literal">ER_ERROR_ON_MASTER</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Query partially completed on the master (error on master:
      %d) and was aborted. There is a chance that your master is
      inconsistent at this point. If you are sure that your master is
      ok, run this query manually on the slave and then restart the
      slave with SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVE;.
      Query:'%s'
    </p></li><li class="listitem"><p><a name="error_er_inconsistent_error"></a>
      <a class="indexterm" name="idm46734187024864"></a>

      <a class="indexterm" name="idm46734187023824"></a>

      Error number: <code class="literal">3002</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_inconsistent_error"><code class="literal">ER_INCONSISTENT_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Query caused different errors on master and slave. Error
      on master: message (format)='%s' error code=%d; Error on
      slave:actual message='%s', error code=%d. Default database:'%s'.
      Query:'%s'
    </p></li><li class="listitem"><p><a name="error_er_storage_engine_not_loaded"></a>
      <a class="indexterm" name="idm46734187017680"></a>

      <a class="indexterm" name="idm46734187016640"></a>

      Error number: <code class="literal">3003</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_storage_engine_not_loaded"><code class="literal">ER_STORAGE_ENGINE_NOT_LOADED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Storage engine for table '%s'.'%s' is not loaded.
    </p></li><li class="listitem"><p><a name="error_er_get_stacked_da_without_active_handler"></a>
      <a class="indexterm" name="idm46734187010512"></a>

      <a class="indexterm" name="idm46734187009472"></a>

      Error number: <code class="literal">3004</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_get_stacked_da_without_active_handler"><code class="literal">ER_GET_STACKED_DA_WITHOUT_ACTIVE_HANDLER</code></a>;
      SQLSTATE: <code class="literal">0Z002</code>
    </p><p>
      Message: GET STACKED DIAGNOSTICS when handler not active
    </p></li><li class="listitem"><p><a name="error_er_warn_legacy_syntax_converted"></a>
      <a class="indexterm" name="idm46734187003328"></a>

      <a class="indexterm" name="idm46734187002224"></a>

      Error number: <code class="literal">3005</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_legacy_syntax_converted"><code class="literal">ER_WARN_LEGACY_SYNTAX_CONVERTED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: %s is no longer supported. The statement was converted to
      %s.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_fulltext_plugin"></a>
      <a class="indexterm" name="idm46734186996160"></a>

      <a class="indexterm" name="idm46734186995056"></a>

      Error number: <code class="literal">3006</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_fulltext_plugin"><code class="literal">ER_BINLOG_UNSAFE_FULLTEXT_PLUGIN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Statement is unsafe because it uses a fulltext parser
      plugin which may not return the same value on the slave.
    </p><p>
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_fulltext_plugin"><code class="literal">ER_BINLOG_UNSAFE_FULLTEXT_PLUGIN</code></a>
      was added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_cannot_discard_temporary_table"></a>
      <a class="indexterm" name="idm46734186987328"></a>

      <a class="indexterm" name="idm46734186986224"></a>

      Error number: <code class="literal">3007</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cannot_discard_temporary_table"><code class="literal">ER_CANNOT_DISCARD_TEMPORARY_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot DISCARD/IMPORT tablespace associated with
      temporary table
    </p><p>
      <a class="link" href="error-handling.html#error_er_cannot_discard_temporary_table"><code class="literal">ER_CANNOT_DISCARD_TEMPORARY_TABLE</code></a>
      was added in 5.7.1.
    </p></li><li class="listitem"><p><a name="error_er_fk_depth_exceeded"></a>
      <a class="indexterm" name="idm46734186978416"></a>

      <a class="indexterm" name="idm46734186977376"></a>

      Error number: <code class="literal">3008</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_fk_depth_exceeded"><code class="literal">ER_FK_DEPTH_EXCEEDED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Foreign key cascade delete/update exceeds max depth of
      %d.
    </p><p>
      <a class="link" href="error-handling.html#error_er_fk_depth_exceeded"><code class="literal">ER_FK_DEPTH_EXCEEDED</code></a> was added in
      5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_col_count_doesnt_match_please_update_v2"></a>
      <a class="indexterm" name="idm46734186969600"></a>

      <a class="indexterm" name="idm46734186968560"></a>

      Error number: <code class="literal">3009</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_col_count_doesnt_match_please_update_v2"><code class="literal">ER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE_V2</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Column count of %s.%s is wrong. Expected %d, found %d.
      Created with MySQL %d, now running %d. Please use mysql_upgrade to
      fix this error.
    </p><p>
      <a class="link" href="error-handling.html#error_er_col_count_doesnt_match_please_update_v2"><code class="literal">ER_COL_COUNT_DOESNT_MATCH_PLEASE_UPDATE_V2</code></a>
      was added in 5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_warn_trigger_doesnt_have_created"></a>
      <a class="indexterm" name="idm46734186960592"></a>

      <a class="indexterm" name="idm46734186959552"></a>

      Error number: <code class="literal">3010</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_trigger_doesnt_have_created"><code class="literal">ER_WARN_TRIGGER_DOESNT_HAVE_CREATED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Trigger %s.%s.%s does not have CREATED attribute.
    </p><p>
      <a class="link" href="error-handling.html#error_er_warn_trigger_doesnt_have_created"><code class="literal">ER_WARN_TRIGGER_DOESNT_HAVE_CREATED</code></a>
      was added in 5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_referenced_trg_does_not_exist"></a>
      <a class="indexterm" name="idm46734186951728"></a>

      <a class="indexterm" name="idm46734186950624"></a>

      Error number: <code class="literal">3011</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_referenced_trg_does_not_exist"><code class="literal">ER_REFERENCED_TRG_DOES_NOT_EXIST</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Referenced trigger '%s' for the given action time and
      event type does not exist.
    </p><p>
      <a class="link" href="error-handling.html#error_er_referenced_trg_does_not_exist"><code class="literal">ER_REFERENCED_TRG_DOES_NOT_EXIST</code></a>
      was added in 5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_explain_not_supported"></a>
      <a class="indexterm" name="idm46734186942800"></a>

      <a class="indexterm" name="idm46734186941760"></a>

      Error number: <code class="literal">3012</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_explain_not_supported"><code class="literal">ER_EXPLAIN_NOT_SUPPORTED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: EXPLAIN FOR CONNECTION command is supported only for
      SELECT/UPDATE/INSERT/DELETE/REPLACE
    </p><p>
      <a class="link" href="error-handling.html#error_er_explain_not_supported"><code class="literal">ER_EXPLAIN_NOT_SUPPORTED</code></a> was added
      in 5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_invalid_field_size"></a>
      <a class="indexterm" name="idm46734186934016"></a>

      <a class="indexterm" name="idm46734186932976"></a>

      Error number: <code class="literal">3013</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_field_size"><code class="literal">ER_INVALID_FIELD_SIZE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Invalid size for column '%s'.
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_field_size"><code class="literal">ER_INVALID_FIELD_SIZE</code></a> was added in
      5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_missing_ha_create_option"></a>
      <a class="indexterm" name="idm46734186925344"></a>

      <a class="indexterm" name="idm46734186924304"></a>

      Error number: <code class="literal">3014</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_missing_ha_create_option"><code class="literal">ER_MISSING_HA_CREATE_OPTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Table storage engine '%s' found required create option
      missing
    </p><p>
      <a class="link" href="error-handling.html#error_er_missing_ha_create_option"><code class="literal">ER_MISSING_HA_CREATE_OPTION</code></a> was
      added in 5.7.2.
    </p></li><li class="listitem"><p><a name="error_er_engine_out_of_memory"></a>
      <a class="indexterm" name="idm46734186916576"></a>

      <a class="indexterm" name="idm46734186915536"></a>

      Error number: <code class="literal">3015</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_engine_out_of_memory"><code class="literal">ER_ENGINE_OUT_OF_MEMORY</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Out of memory in storage engine '%s'.
    </p><p>
      <a class="link" href="error-handling.html#error_er_engine_out_of_memory"><code class="literal">ER_ENGINE_OUT_OF_MEMORY</code></a> was added
      in 5.7.3.
    </p></li><li class="listitem"><p><a name="error_er_password_expire_anonymous_user"></a>
      <a class="indexterm" name="idm46734186907888"></a>

      <a class="indexterm" name="idm46734186906784"></a>

      Error number: <code class="literal">3016</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_password_expire_anonymous_user"><code class="literal">ER_PASSWORD_EXPIRE_ANONYMOUS_USER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The password for anonymous user cannot be expired.
    </p><p>
      <a class="link" href="error-handling.html#error_er_password_expire_anonymous_user"><code class="literal">ER_PASSWORD_EXPIRE_ANONYMOUS_USER</code></a>
      was added in 5.7.3.
    </p></li><li class="listitem"><p><a name="error_er_slave_sql_thread_must_stop"></a>
      <a class="indexterm" name="idm46734186899072"></a>

      <a class="indexterm" name="idm46734186897968"></a>

      Error number: <code class="literal">3017</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_sql_thread_must_stop"><code class="literal">ER_SLAVE_SQL_THREAD_MUST_STOP</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: This operation cannot be performed with a running slave
      sql thread; run STOP SLAVE SQL_THREAD first
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_sql_thread_must_stop"><code class="literal">ER_SLAVE_SQL_THREAD_MUST_STOP</code></a> was
      added in 5.7.3.
    </p></li><li class="listitem"><p><a name="error_er_no_ft_materialized_subquery"></a>
      <a class="indexterm" name="idm46734186890256"></a>

      <a class="indexterm" name="idm46734186889152"></a>

      Error number: <code class="literal">3018</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_ft_materialized_subquery"><code class="literal">ER_NO_FT_MATERIALIZED_SUBQUERY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot create FULLTEXT index on materialized subquery
    </p><p>
      <a class="link" href="error-handling.html#error_er_no_ft_materialized_subquery"><code class="literal">ER_NO_FT_MATERIALIZED_SUBQUERY</code></a> was
      added in 5.7.4.
    </p></li><li class="listitem"><p><a name="error_er_innodb_undo_log_full"></a>
      <a class="indexterm" name="idm46734186881488"></a>

      <a class="indexterm" name="idm46734186880448"></a>

      Error number: <code class="literal">3019</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_innodb_undo_log_full"><code class="literal">ER_INNODB_UNDO_LOG_FULL</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Undo Log error: %s
    </p><p>
      <a class="link" href="error-handling.html#error_er_innodb_undo_log_full"><code class="literal">ER_INNODB_UNDO_LOG_FULL</code></a> was added
      in 5.7.4.
    </p></li><li class="listitem"><p><a name="error_er_invalid_argument_for_logarithm"></a>
      <a class="indexterm" name="idm46734186872880"></a>

      <a class="indexterm" name="idm46734186871776"></a>

      Error number: <code class="literal">3020</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_argument_for_logarithm"><code class="literal">ER_INVALID_ARGUMENT_FOR_LOGARITHM</code></a>;
      SQLSTATE: <code class="literal">2201E</code>
    </p><p>
      Message: Invalid argument for logarithm
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_argument_for_logarithm"><code class="literal">ER_INVALID_ARGUMENT_FOR_LOGARITHM</code></a>
      was added in 5.7.4.
    </p></li><li class="listitem"><p><a name="error_er_slave_channel_io_thread_must_stop"></a>
      <a class="indexterm" name="idm46734186864096"></a>

      <a class="indexterm" name="idm46734186863056"></a>

      Error number: <code class="literal">3021</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_channel_io_thread_must_stop"><code class="literal">ER_SLAVE_CHANNEL_IO_THREAD_MUST_STOP</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: This operation cannot be performed with a running slave
      io thread; run STOP SLAVE IO_THREAD FOR CHANNEL '%s' first.
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_channel_io_thread_must_stop"><code class="literal">ER_SLAVE_CHANNEL_IO_THREAD_MUST_STOP</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_warn_open_temp_tables_must_be_zero"></a>
      <a class="indexterm" name="idm46734186855088"></a>

      <a class="indexterm" name="idm46734186854048"></a>

      Error number: <code class="literal">3022</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_open_temp_tables_must_be_zero"><code class="literal">ER_WARN_OPEN_TEMP_TABLES_MUST_BE_ZERO</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: This operation may not be safe when the slave has
      temporary tables. The tables will be kept open until the server
      restarts or until the tables are deleted by any replicated DROP
      statement. Suggest to wait until slave_open_temp_tables = 0.
    </p><p>
      <a class="link" href="error-handling.html#error_er_warn_open_temp_tables_must_be_zero"><code class="literal">ER_WARN_OPEN_TEMP_TABLES_MUST_BE_ZERO</code></a>
      was added in 5.7.4.
    </p></li><li class="listitem"><p><a name="error_er_warn_only_master_log_file_no_pos"></a>
      <a class="indexterm" name="idm46734186846032"></a>

      <a class="indexterm" name="idm46734186844992"></a>

      Error number: <code class="literal">3023</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_only_master_log_file_no_pos"><code class="literal">ER_WARN_ONLY_MASTER_LOG_FILE_NO_POS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: CHANGE MASTER TO with a MASTER_LOG_FILE clause but no
      MASTER_LOG_POS clause may not be safe. The old position value may
      not be valid for the new binary log file.
    </p><p>
      <a class="link" href="error-handling.html#error_er_warn_only_master_log_file_no_pos"><code class="literal">ER_WARN_ONLY_MASTER_LOG_FILE_NO_POS</code></a>
      was added in 5.7.4.
    </p></li><li class="listitem"><p><a name="error_er_query_timeout"></a>
      <a class="indexterm" name="idm46734186837024"></a>

      <a class="indexterm" name="idm46734186835968"></a>

      Error number: <code class="literal">3024</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_query_timeout"><code class="literal">ER_QUERY_TIMEOUT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Query execution was interrupted, maximum statement
      execution time exceeded
    </p><p>
      <a class="link" href="error-handling.html#error_er_query_timeout"><code class="literal">ER_QUERY_TIMEOUT</code></a> was added in
      5.7.4.
    </p></li><li class="listitem"><p><a name="error_er_non_ro_select_disable_timer"></a>
      <a class="indexterm" name="idm46734186828288"></a>

      <a class="indexterm" name="idm46734186827184"></a>

      Error number: <code class="literal">3025</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_non_ro_select_disable_timer"><code class="literal">ER_NON_RO_SELECT_DISABLE_TIMER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Select is not a read only statement, disabling timer
    </p><p>
      <a class="link" href="error-handling.html#error_er_non_ro_select_disable_timer"><code class="literal">ER_NON_RO_SELECT_DISABLE_TIMER</code></a> was
      added in 5.7.4.
    </p></li><li class="listitem"><p><a name="error_er_dup_list_entry"></a>
      <a class="indexterm" name="idm46734186819440"></a>

      <a class="indexterm" name="idm46734186818384"></a>

      Error number: <code class="literal">3026</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_dup_list_entry"><code class="literal">ER_DUP_LIST_ENTRY</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Duplicate entry '%s'.
    </p><p>
      <a class="link" href="error-handling.html#error_er_dup_list_entry"><code class="literal">ER_DUP_LIST_ENTRY</code></a> was added in
      5.7.4.
    </p></li><li class="listitem"><p><a name="error_er_sql_mode_no_effect"></a>
      <a class="indexterm" name="idm46734186810752"></a>

      <a class="indexterm" name="idm46734186809712"></a>

      Error number: <code class="literal">3027</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sql_mode_no_effect"><code class="literal">ER_SQL_MODE_NO_EFFECT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: '%s' mode no longer has any effect. Use STRICT_ALL_TABLES
      or STRICT_TRANS_TABLES instead.
    </p><p>
      <a class="link" href="error-handling.html#error_er_sql_mode_no_effect"><code class="literal">ER_SQL_MODE_NO_EFFECT</code></a> was added in
      5.7.4.
    </p></li><li class="listitem"><p><a name="error_er_aggregate_order_for_union"></a>
      <a class="indexterm" name="idm46734186802000"></a>

      <a class="indexterm" name="idm46734186800960"></a>

      Error number: <code class="literal">3028</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_aggregate_order_for_union"><code class="literal">ER_AGGREGATE_ORDER_FOR_UNION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Expression #%u of ORDER BY contains aggregate function
      and applies to a UNION
    </p><p>
      <a class="link" href="error-handling.html#error_er_aggregate_order_for_union"><code class="literal">ER_AGGREGATE_ORDER_FOR_UNION</code></a> was
      added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_aggregate_order_non_agg_query"></a>
      <a class="indexterm" name="idm46734186793280"></a>

      <a class="indexterm" name="idm46734186792176"></a>

      Error number: <code class="literal">3029</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_aggregate_order_non_agg_query"><code class="literal">ER_AGGREGATE_ORDER_NON_AGG_QUERY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Expression #%u of ORDER BY contains aggregate function
      and applies to the result of a non-aggregated query
    </p><p>
      <a class="link" href="error-handling.html#error_er_aggregate_order_non_agg_query"><code class="literal">ER_AGGREGATE_ORDER_NON_AGG_QUERY</code></a>
      was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_slave_worker_stopped_previous_thd_error"></a>
      <a class="indexterm" name="idm46734186784288"></a>

      <a class="indexterm" name="idm46734186783248"></a>

      Error number: <code class="literal">3030</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_worker_stopped_previous_thd_error"><code class="literal">ER_SLAVE_WORKER_STOPPED_PREVIOUS_THD_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Slave worker has stopped after at least one previous
      worker encountered an error when slave-preserve-commit-order was
      enabled. To preserve commit order, the last transaction executed
      by this thread has not been committed. When restarting the slave
      after fixing any failed threads, you should fix this worker as
      well.
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_worker_stopped_previous_thd_error"><code class="literal">ER_SLAVE_WORKER_STOPPED_PREVIOUS_THD_ERROR</code></a>
      was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_dont_support_slave_preserve_commit_order"></a>
      <a class="indexterm" name="idm46734186775088"></a>

      <a class="indexterm" name="idm46734186774048"></a>

      Error number: <code class="literal">3031</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_dont_support_slave_preserve_commit_order"><code class="literal">ER_DONT_SUPPORT_SLAVE_PRESERVE_COMMIT_ORDER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: slave_preserve_commit_order is not supported %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_dont_support_slave_preserve_commit_order"><code class="literal">ER_DONT_SUPPORT_SLAVE_PRESERVE_COMMIT_ORDER</code></a>
      was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_server_offline_mode"></a>
      <a class="indexterm" name="idm46734186766288"></a>

      <a class="indexterm" name="idm46734186765248"></a>

      Error number: <code class="literal">3032</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_server_offline_mode"><code class="literal">ER_SERVER_OFFLINE_MODE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The server is currently in offline mode
    </p><p>
      <a class="link" href="error-handling.html#error_er_server_offline_mode"><code class="literal">ER_SERVER_OFFLINE_MODE</code></a> was added
      in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_gis_different_srids"></a>
      <a class="indexterm" name="idm46734186757648"></a>

      <a class="indexterm" name="idm46734186756608"></a>

      Error number: <code class="literal">3033</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gis_different_srids"><code class="literal">ER_GIS_DIFFERENT_SRIDS</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Binary geometry function %s given two geometries of
      different srids: %u and %u, which should have been identical.
    </p><p>
      Geometry values passed as arguments to spatial functions must have
      the same SRID value.
    </p><p>
      <a class="link" href="error-handling.html#error_er_gis_different_srids"><code class="literal">ER_GIS_DIFFERENT_SRIDS</code></a> was added
      in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_gis_unsupported_argument"></a>
      <a class="indexterm" name="idm46734186748416"></a>

      <a class="indexterm" name="idm46734186747376"></a>

      Error number: <code class="literal">3034</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gis_unsupported_argument"><code class="literal">ER_GIS_UNSUPPORTED_ARGUMENT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Calling geometry function %s with unsupported types of
      arguments.
    </p><p>
      A spatial function was called with a combination of argument types
      that the function does not support.
    </p><p>
      <a class="link" href="error-handling.html#error_er_gis_unsupported_argument"><code class="literal">ER_GIS_UNSUPPORTED_ARGUMENT</code></a> was
      added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_gis_unknown_error"></a>
      <a class="indexterm" name="idm46734186739184"></a>

      <a class="indexterm" name="idm46734186738144"></a>

      Error number: <code class="literal">3035</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gis_unknown_error"><code class="literal">ER_GIS_UNKNOWN_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Unknown GIS error occured in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_gis_unknown_error"><code class="literal">ER_GIS_UNKNOWN_ERROR</code></a> was added in
      5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_gis_unknown_exception"></a>
      <a class="indexterm" name="idm46734186730432"></a>

      <a class="indexterm" name="idm46734186729392"></a>

      Error number: <code class="literal">3036</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gis_unknown_exception"><code class="literal">ER_GIS_UNKNOWN_EXCEPTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Unknown exception caught in GIS function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_gis_unknown_exception"><code class="literal">ER_GIS_UNKNOWN_EXCEPTION</code></a> was added
      in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_gis_invalid_data"></a>
      <a class="indexterm" name="idm46734186721744"></a>

      <a class="indexterm" name="idm46734186720704"></a>

      Error number: <code class="literal">3037</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gis_invalid_data"><code class="literal">ER_GIS_INVALID_DATA</code></a>; SQLSTATE:
      <code class="literal">22023</code>
    </p><p>
      Message: Invalid GIS data provided to function %s.
    </p><p>
      A spatial function was called with an argument not recognized as a
      valid geometry value.
    </p><p>
      <a class="link" href="error-handling.html#error_er_gis_invalid_data"><code class="literal">ER_GIS_INVALID_DATA</code></a> was added in
      5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_boost_geometry_empty_input_exception"></a>
      <a class="indexterm" name="idm46734186712496"></a>

      <a class="indexterm" name="idm46734186711456"></a>

      Error number: <code class="literal">3038</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_boost_geometry_empty_input_exception"><code class="literal">ER_BOOST_GEOMETRY_EMPTY_INPUT_EXCEPTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The geometry has no data in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_boost_geometry_empty_input_exception"><code class="literal">ER_BOOST_GEOMETRY_EMPTY_INPUT_EXCEPTION</code></a>
      was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_boost_geometry_centroid_exception"></a>
      <a class="indexterm" name="idm46734186703584"></a>

      <a class="indexterm" name="idm46734186702544"></a>

      Error number: <code class="literal">3039</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_boost_geometry_centroid_exception"><code class="literal">ER_BOOST_GEOMETRY_CENTROID_EXCEPTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Unable to calculate centroid because geometry is empty in
      function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_boost_geometry_centroid_exception"><code class="literal">ER_BOOST_GEOMETRY_CENTROID_EXCEPTION</code></a>
      was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_boost_geometry_overlay_invalid_input_exception"></a>
      <a class="indexterm" name="idm46734186694640"></a>

      <a class="indexterm" name="idm46734186693520"></a>

      Error number: <code class="literal">3040</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_boost_geometry_overlay_invalid_input_exception"><code class="literal">ER_BOOST_GEOMETRY_OVERLAY_INVALID_INPUT_EXCEPTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Geometry overlay calculation error: geometry data is
      invalid in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_boost_geometry_overlay_invalid_input_exception"><code class="literal">ER_BOOST_GEOMETRY_OVERLAY_INVALID_INPUT_EXCEPTION</code></a>
      was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_boost_geometry_turn_info_exception"></a>
      <a class="indexterm" name="idm46734186685632"></a>

      <a class="indexterm" name="idm46734186684592"></a>

      Error number: <code class="literal">3041</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_boost_geometry_turn_info_exception"><code class="literal">ER_BOOST_GEOMETRY_TURN_INFO_EXCEPTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Geometry turn info calculation error: geometry data is
      invalid in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_boost_geometry_turn_info_exception"><code class="literal">ER_BOOST_GEOMETRY_TURN_INFO_EXCEPTION</code></a>
      was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_boost_geometry_self_intersection_point_exception"></a>
      <a class="indexterm" name="idm46734186676688"></a>

      <a class="indexterm" name="idm46734186675648"></a>

      Error number: <code class="literal">3042</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_boost_geometry_self_intersection_point_exception"><code class="literal">ER_BOOST_GEOMETRY_SELF_INTERSECTION_POINT_EXCEPTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Analysis procedures of intersection points interrupted
      unexpectedly in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_boost_geometry_self_intersection_point_exception"><code class="literal">ER_BOOST_GEOMETRY_SELF_INTERSECTION_POINT_EXCEPTION</code></a>
      was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_boost_geometry_unknown_exception"></a>
      <a class="indexterm" name="idm46734186667600"></a>

      <a class="indexterm" name="idm46734186666560"></a>

      Error number: <code class="literal">3043</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_boost_geometry_unknown_exception"><code class="literal">ER_BOOST_GEOMETRY_UNKNOWN_EXCEPTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Unknown exception thrown in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_boost_geometry_unknown_exception"><code class="literal">ER_BOOST_GEOMETRY_UNKNOWN_EXCEPTION</code></a>
      was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_std_bad_alloc_error"></a>
      <a class="indexterm" name="idm46734186658816"></a>

      <a class="indexterm" name="idm46734186657776"></a>

      Error number: <code class="literal">3044</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_std_bad_alloc_error"><code class="literal">ER_STD_BAD_ALLOC_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Memory allocation error: %s in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_std_bad_alloc_error"><code class="literal">ER_STD_BAD_ALLOC_ERROR</code></a> was added
      in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_std_domain_error"></a>
      <a class="indexterm" name="idm46734186650128"></a>

      <a class="indexterm" name="idm46734186649088"></a>

      Error number: <code class="literal">3045</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_std_domain_error"><code class="literal">ER_STD_DOMAIN_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Domain error: %s in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_std_domain_error"><code class="literal">ER_STD_DOMAIN_ERROR</code></a> was added in
      5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_std_length_error"></a>
      <a class="indexterm" name="idm46734186641440"></a>

      <a class="indexterm" name="idm46734186640400"></a>

      Error number: <code class="literal">3046</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_std_length_error"><code class="literal">ER_STD_LENGTH_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Length error: %s in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_std_length_error"><code class="literal">ER_STD_LENGTH_ERROR</code></a> was added in
      5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_std_invalid_argument"></a>
      <a class="indexterm" name="idm46734186632768"></a>

      <a class="indexterm" name="idm46734186631728"></a>

      Error number: <code class="literal">3047</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_std_invalid_argument"><code class="literal">ER_STD_INVALID_ARGUMENT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Invalid argument error: %s in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_std_invalid_argument"><code class="literal">ER_STD_INVALID_ARGUMENT</code></a> was added
      in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_std_out_of_range_error"></a>
      <a class="indexterm" name="idm46734186624016"></a>

      <a class="indexterm" name="idm46734186622976"></a>

      Error number: <code class="literal">3048</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_std_out_of_range_error"><code class="literal">ER_STD_OUT_OF_RANGE_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Out of range error: %s in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_std_out_of_range_error"><code class="literal">ER_STD_OUT_OF_RANGE_ERROR</code></a> was
      added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_std_overflow_error"></a>
      <a class="indexterm" name="idm46734186615152"></a>

      <a class="indexterm" name="idm46734186614112"></a>

      Error number: <code class="literal">3049</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_std_overflow_error"><code class="literal">ER_STD_OVERFLOW_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Overflow error error: %s in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_std_overflow_error"><code class="literal">ER_STD_OVERFLOW_ERROR</code></a> was added in
      5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_std_range_error"></a>
      <a class="indexterm" name="idm46734186606464"></a>

      <a class="indexterm" name="idm46734186605424"></a>

      Error number: <code class="literal">3050</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_std_range_error"><code class="literal">ER_STD_RANGE_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Range error: %s in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_std_range_error"><code class="literal">ER_STD_RANGE_ERROR</code></a> was added in
      5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_std_underflow_error"></a>
      <a class="indexterm" name="idm46734186597792"></a>

      <a class="indexterm" name="idm46734186596752"></a>

      Error number: <code class="literal">3051</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_std_underflow_error"><code class="literal">ER_STD_UNDERFLOW_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Underflow error: %s in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_std_underflow_error"><code class="literal">ER_STD_UNDERFLOW_ERROR</code></a> was added
      in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_std_logic_error"></a>
      <a class="indexterm" name="idm46734186589040"></a>

      <a class="indexterm" name="idm46734186588000"></a>

      Error number: <code class="literal">3052</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_std_logic_error"><code class="literal">ER_STD_LOGIC_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Logic error: %s in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_std_logic_error"><code class="literal">ER_STD_LOGIC_ERROR</code></a> was added in
      5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_std_runtime_error"></a>
      <a class="indexterm" name="idm46734186580304"></a>

      <a class="indexterm" name="idm46734186579264"></a>

      Error number: <code class="literal">3053</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_std_runtime_error"><code class="literal">ER_STD_RUNTIME_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Runtime error: %s in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_std_runtime_error"><code class="literal">ER_STD_RUNTIME_ERROR</code></a> was added in
      5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_std_unknown_exception"></a>
      <a class="indexterm" name="idm46734186571632"></a>

      <a class="indexterm" name="idm46734186570592"></a>

      Error number: <code class="literal">3054</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_std_unknown_exception"><code class="literal">ER_STD_UNKNOWN_EXCEPTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Unknown exception: %s in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_std_unknown_exception"><code class="literal">ER_STD_UNKNOWN_EXCEPTION</code></a> was added
      in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_gis_data_wrong_endianess"></a>
      <a class="indexterm" name="idm46734186562832"></a>

      <a class="indexterm" name="idm46734186561792"></a>

      Error number: <code class="literal">3055</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gis_data_wrong_endianess"><code class="literal">ER_GIS_DATA_WRONG_ENDIANESS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Geometry byte string must be little endian.
    </p><p>
      <a class="link" href="error-handling.html#error_er_gis_data_wrong_endianess"><code class="literal">ER_GIS_DATA_WRONG_ENDIANESS</code></a> was
      added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_change_master_password_length"></a>
      <a class="indexterm" name="idm46734186553968"></a>

      <a class="indexterm" name="idm46734186552864"></a>

      Error number: <code class="literal">3056</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_change_master_password_length"><code class="literal">ER_CHANGE_MASTER_PASSWORD_LENGTH</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The password provided for the replication user exceeds
      the maximum length of 32 characters
    </p><p>
      <a class="link" href="error-handling.html#error_er_change_master_password_length"><code class="literal">ER_CHANGE_MASTER_PASSWORD_LENGTH</code></a>
      was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_user_lock_wrong_name"></a>
      <a class="indexterm" name="idm46734186545168"></a>

      <a class="indexterm" name="idm46734186544128"></a>

      Error number: <code class="literal">3057</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_user_lock_wrong_name"><code class="literal">ER_USER_LOCK_WRONG_NAME</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Incorrect user-level lock name '%s'.
    </p><p>
      <a class="link" href="error-handling.html#error_er_user_lock_wrong_name"><code class="literal">ER_USER_LOCK_WRONG_NAME</code></a> was added
      in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_user_lock_deadlock"></a>
      <a class="indexterm" name="idm46734186536528"></a>

      <a class="indexterm" name="idm46734186535488"></a>

      Error number: <code class="literal">3058</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_user_lock_deadlock"><code class="literal">ER_USER_LOCK_DEADLOCK</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Deadlock found when trying to get user-level lock; try
      rolling back transaction/releasing locks and restarting lock
      acquisition.
    </p><p>
      This error is returned when the metdata locking subsystem detects
      a deadlock for an attempt to acquire a named lock with
      <a class="link" href="functions.html#function_get-lock"><code class="literal">GET_LOCK</code></a>.
    </p><p>
      <a class="link" href="error-handling.html#error_er_user_lock_deadlock"><code class="literal">ER_USER_LOCK_DEADLOCK</code></a> was added in
      5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_replace_inaccessible_rows"></a>
      <a class="indexterm" name="idm46734186526032"></a>

      <a class="indexterm" name="idm46734186524992"></a>

      Error number: <code class="literal">3059</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_replace_inaccessible_rows"><code class="literal">ER_REPLACE_INACCESSIBLE_ROWS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: REPLACE cannot be executed as it requires deleting rows
      that are not in the view
    </p><p>
      <a class="link" href="error-handling.html#error_er_replace_inaccessible_rows"><code class="literal">ER_REPLACE_INACCESSIBLE_ROWS</code></a> was
      added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_alter_operation_not_supported_reason_gis"></a>
      <a class="indexterm" name="idm46734186517136"></a>

      <a class="indexterm" name="idm46734186516096"></a>

      Error number: <code class="literal">3060</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_gis"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_GIS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Do not support online operation on table with GIS index
    </p><p>
      <a class="link" href="error-handling.html#error_er_alter_operation_not_supported_reason_gis"><code class="literal">ER_ALTER_OPERATION_NOT_SUPPORTED_REASON_GIS</code></a>
      was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_illegal_user_var"></a>
      <a class="indexterm" name="idm46734186508256"></a>

      <a class="indexterm" name="idm46734186507216"></a>

      Error number: <code class="literal">3061</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_illegal_user_var"><code class="literal">ER_ILLEGAL_USER_VAR</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: User variable name '%s' is illegal
    </p><p>
      <a class="link" href="error-handling.html#error_er_illegal_user_var"><code class="literal">ER_ILLEGAL_USER_VAR</code></a> was added in
      5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_gtid_mode_off"></a>
      <a class="indexterm" name="idm46734186499632"></a>

      <a class="indexterm" name="idm46734186498576"></a>

      Error number: <code class="literal">3062</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gtid_mode_off"><code class="literal">ER_GTID_MODE_OFF</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Cannot %s when GTID_MODE = OFF.
    </p><p>
      <a class="link" href="error-handling.html#error_er_gtid_mode_off"><code class="literal">ER_GTID_MODE_OFF</code></a> was added in
      5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_unsupported_by_replication_thread"></a>
      <a class="indexterm" name="idm46734186490896"></a>

      <a class="indexterm" name="idm46734186489856"></a>

      Error number: <code class="literal">3063</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unsupported_by_replication_thread"><code class="literal">ER_UNSUPPORTED_BY_REPLICATION_THREAD</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot %s from a replication slave thread.
    </p><p>
      <a class="link" href="error-handling.html#error_er_unsupported_by_replication_thread"><code class="literal">ER_UNSUPPORTED_BY_REPLICATION_THREAD</code></a>
      was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_incorrect_type"></a>
      <a class="indexterm" name="idm46734186482016"></a>

      <a class="indexterm" name="idm46734186480960"></a>

      Error number: <code class="literal">3064</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_incorrect_type"><code class="literal">ER_INCORRECT_TYPE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Incorrect type for argument %s in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_incorrect_type"><code class="literal">ER_INCORRECT_TYPE</code></a> was added in
      5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_field_in_order_not_select"></a>
      <a class="indexterm" name="idm46734186473312"></a>

      <a class="indexterm" name="idm46734186472272"></a>

      Error number: <code class="literal">3065</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_field_in_order_not_select"><code class="literal">ER_FIELD_IN_ORDER_NOT_SELECT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Expression #%u of ORDER BY clause is not in SELECT list,
      references column '%s' which is not in SELECT list; this is
      incompatible with %s
    </p><p>
      <a class="link" href="error-handling.html#error_er_field_in_order_not_select"><code class="literal">ER_FIELD_IN_ORDER_NOT_SELECT</code></a> was
      added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_aggregate_in_order_not_select"></a>
      <a class="indexterm" name="idm46734186464464"></a>

      <a class="indexterm" name="idm46734186463360"></a>

      Error number: <code class="literal">3066</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_aggregate_in_order_not_select"><code class="literal">ER_AGGREGATE_IN_ORDER_NOT_SELECT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Expression #%u of ORDER BY clause is not in SELECT list,
      contains aggregate function; this is incompatible with %s
    </p><p>
      <a class="link" href="error-handling.html#error_er_aggregate_in_order_not_select"><code class="literal">ER_AGGREGATE_IN_ORDER_NOT_SELECT</code></a>
      was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_invalid_rpl_wild_table_filter_pattern"></a>
      <a class="indexterm" name="idm46734186455584"></a>

      <a class="indexterm" name="idm46734186454544"></a>

      Error number: <code class="literal">3067</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_rpl_wild_table_filter_pattern"><code class="literal">ER_INVALID_RPL_WILD_TABLE_FILTER_PATTERN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Supplied filter list contains a value which is not in the
      required format 'db_pattern.table_pattern'
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_rpl_wild_table_filter_pattern"><code class="literal">ER_INVALID_RPL_WILD_TABLE_FILTER_PATTERN</code></a>
      was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_net_ok_packet_too_large"></a>
      <a class="indexterm" name="idm46734186446608"></a>

      <a class="indexterm" name="idm46734186445568"></a>

      Error number: <code class="literal">3068</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_net_ok_packet_too_large"><code class="literal">ER_NET_OK_PACKET_TOO_LARGE</code></a>;
      SQLSTATE: <code class="literal">08S01</code>
    </p><p>
      Message: OK packet too large
    </p><p>
      <a class="link" href="error-handling.html#error_er_net_ok_packet_too_large"><code class="literal">ER_NET_OK_PACKET_TOO_LARGE</code></a> was
      added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_invalid_json_data"></a>
      <a class="indexterm" name="idm46734186437760"></a>

      <a class="indexterm" name="idm46734186436720"></a>

      Error number: <code class="literal">3069</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_json_data"><code class="literal">ER_INVALID_JSON_DATA</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Invalid JSON data provided to function %s: %s
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_json_data"><code class="literal">ER_INVALID_JSON_DATA</code></a> was added in
      5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_invalid_geojson_missing_member"></a>
      <a class="indexterm" name="idm46734186429008"></a>

      <a class="indexterm" name="idm46734186427904"></a>

      Error number: <code class="literal">3070</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_geojson_missing_member"><code class="literal">ER_INVALID_GEOJSON_MISSING_MEMBER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Invalid GeoJSON data provided to function %s: Missing
      required member '%s'
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_geojson_missing_member"><code class="literal">ER_INVALID_GEOJSON_MISSING_MEMBER</code></a>
      was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_invalid_geojson_wrong_type"></a>
      <a class="indexterm" name="idm46734186420160"></a>

      <a class="indexterm" name="idm46734186419056"></a>

      Error number: <code class="literal">3071</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_geojson_wrong_type"><code class="literal">ER_INVALID_GEOJSON_WRONG_TYPE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Invalid GeoJSON data provided to function %s: Member '%s'
      must be of type '%s'
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_geojson_wrong_type"><code class="literal">ER_INVALID_GEOJSON_WRONG_TYPE</code></a> was
      added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_invalid_geojson_unspecified"></a>
      <a class="indexterm" name="idm46734186411296"></a>

      <a class="indexterm" name="idm46734186410192"></a>

      Error number: <code class="literal">3072</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_geojson_unspecified"><code class="literal">ER_INVALID_GEOJSON_UNSPECIFIED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Invalid GeoJSON data provided to function %s
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_geojson_unspecified"><code class="literal">ER_INVALID_GEOJSON_UNSPECIFIED</code></a> was
      added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_dimension_unsupported"></a>
      <a class="indexterm" name="idm46734186402480"></a>

      <a class="indexterm" name="idm46734186401440"></a>

      Error number: <code class="literal">3073</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_dimension_unsupported"><code class="literal">ER_DIMENSION_UNSUPPORTED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Unsupported number of coordinate dimensions in function
      %s: Found %u, expected %u
    </p><p>
      <a class="link" href="error-handling.html#error_er_dimension_unsupported"><code class="literal">ER_DIMENSION_UNSUPPORTED</code></a> was added
      in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_er_slave_channel_does_not_exist"></a>
      <a class="indexterm" name="idm46734186393568"></a>

      <a class="indexterm" name="idm46734186392464"></a>

      Error number: <code class="literal">3074</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_channel_does_not_exist"><code class="literal">ER_SLAVE_CHANNEL_DOES_NOT_EXIST</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Slave channel '%s' does not exist.
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_channel_does_not_exist"><code class="literal">ER_SLAVE_CHANNEL_DOES_NOT_EXIST</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_slave_multiple_channels_host_port"></a>
      <a class="indexterm" name="idm46734186384720"></a>

      <a class="indexterm" name="idm46734186383680"></a>

      Error number: <code class="literal">3075</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_multiple_channels_host_port"><code class="literal">ER_SLAVE_MULTIPLE_CHANNELS_HOST_PORT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: A slave channel '%s' already exists for the given host
      and port combination.
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_multiple_channels_host_port"><code class="literal">ER_SLAVE_MULTIPLE_CHANNELS_HOST_PORT</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_slave_channel_name_invalid_or_too_long"></a>
      <a class="indexterm" name="idm46734186375840"></a>

      <a class="indexterm" name="idm46734186374800"></a>

      Error number: <code class="literal">3076</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_channel_name_invalid_or_too_long"><code class="literal">ER_SLAVE_CHANNEL_NAME_INVALID_OR_TOO_LONG</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Couldn't create channel: Channel name is either invalid
      or too long.
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_channel_name_invalid_or_too_long"><code class="literal">ER_SLAVE_CHANNEL_NAME_INVALID_OR_TOO_LONG</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_slave_new_channel_wrong_repository"></a>
      <a class="indexterm" name="idm46734186366896"></a>

      <a class="indexterm" name="idm46734186365856"></a>

      Error number: <code class="literal">3077</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_new_channel_wrong_repository"><code class="literal">ER_SLAVE_NEW_CHANNEL_WRONG_REPOSITORY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: To have multiple channels, repository cannot be of type
      FILE; Please check the repository configuration and convert them
      to TABLE.
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_new_channel_wrong_repository"><code class="literal">ER_SLAVE_NEW_CHANNEL_WRONG_REPOSITORY</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_slave_channel_delete"></a>
      <a class="indexterm" name="idm46734186358064"></a>

      <a class="indexterm" name="idm46734186357024"></a>

      Error number: <code class="literal">3078</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_channel_delete"><code class="literal">ER_SLAVE_CHANNEL_DELETE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Cannot delete slave info objects for channel '%s'.
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_channel_delete"><code class="literal">ER_SLAVE_CHANNEL_DELETE</code></a> was added
      in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_slave_multiple_channels_cmd"></a>
      <a class="indexterm" name="idm46734186349248"></a>

      <a class="indexterm" name="idm46734186348144"></a>

      Error number: <code class="literal">3079</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_multiple_channels_cmd"><code class="literal">ER_SLAVE_MULTIPLE_CHANNELS_CMD</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Multiple channels exist on the slave. Please provide
      channel name as an argument.
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_multiple_channels_cmd"><code class="literal">ER_SLAVE_MULTIPLE_CHANNELS_CMD</code></a> was
      added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_slave_max_channels_exceeded"></a>
      <a class="indexterm" name="idm46734186340320"></a>

      <a class="indexterm" name="idm46734186339216"></a>

      Error number: <code class="literal">3080</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_max_channels_exceeded"><code class="literal">ER_SLAVE_MAX_CHANNELS_EXCEEDED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Maximum number of replication channels allowed exceeded.
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_max_channels_exceeded"><code class="literal">ER_SLAVE_MAX_CHANNELS_EXCEEDED</code></a> was
      added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_slave_channel_must_stop"></a>
      <a class="indexterm" name="idm46734186331552"></a>

      <a class="indexterm" name="idm46734186330512"></a>

      Error number: <code class="literal">3081</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_channel_must_stop"><code class="literal">ER_SLAVE_CHANNEL_MUST_STOP</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: This operation cannot be performed with running
      replication threads; run STOP SLAVE FOR CHANNEL '%s' first
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_channel_must_stop"><code class="literal">ER_SLAVE_CHANNEL_MUST_STOP</code></a> was
      added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_slave_channel_not_running"></a>
      <a class="indexterm" name="idm46734186322688"></a>

      <a class="indexterm" name="idm46734186321648"></a>

      Error number: <code class="literal">3082</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_channel_not_running"><code class="literal">ER_SLAVE_CHANNEL_NOT_RUNNING</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: This operation requires running replication threads;
      configure slave and run START SLAVE FOR CHANNEL '%s'
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_channel_not_running"><code class="literal">ER_SLAVE_CHANNEL_NOT_RUNNING</code></a> was
      added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_slave_channel_was_running"></a>
      <a class="indexterm" name="idm46734186313824"></a>

      <a class="indexterm" name="idm46734186312784"></a>

      Error number: <code class="literal">3083</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_channel_was_running"><code class="literal">ER_SLAVE_CHANNEL_WAS_RUNNING</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Replication thread(s) for channel '%s' are already
      runnning.
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_channel_was_running"><code class="literal">ER_SLAVE_CHANNEL_WAS_RUNNING</code></a> was
      added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_slave_channel_was_not_running"></a>
      <a class="indexterm" name="idm46734186305072"></a>

      <a class="indexterm" name="idm46734186303968"></a>

      Error number: <code class="literal">3084</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_channel_was_not_running"><code class="literal">ER_SLAVE_CHANNEL_WAS_NOT_RUNNING</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Replication thread(s) for channel '%s' are already
      stopped.
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_channel_was_not_running"><code class="literal">ER_SLAVE_CHANNEL_WAS_NOT_RUNNING</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_slave_channel_sql_thread_must_stop"></a>
      <a class="indexterm" name="idm46734186296192"></a>

      <a class="indexterm" name="idm46734186295152"></a>

      Error number: <code class="literal">3085</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_channel_sql_thread_must_stop"><code class="literal">ER_SLAVE_CHANNEL_SQL_THREAD_MUST_STOP</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: This operation cannot be performed with a running slave
      sql thread; run STOP SLAVE SQL_THREAD FOR CHANNEL '%s' first.
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_channel_sql_thread_must_stop"><code class="literal">ER_SLAVE_CHANNEL_SQL_THREAD_MUST_STOP</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_slave_channel_sql_skip_counter"></a>
      <a class="indexterm" name="idm46734186287312"></a>

      <a class="indexterm" name="idm46734186286208"></a>

      Error number: <code class="literal">3086</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_channel_sql_skip_counter"><code class="literal">ER_SLAVE_CHANNEL_SQL_SKIP_COUNTER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: When sql_slave_skip_counter &gt; 0, it is not allowed to
      start more than one SQL thread by using 'START SLAVE
      [SQL_THREAD]'. Value of sql_slave_skip_counter can only be used by
      one SQL thread at a time. Please use 'START SLAVE [SQL_THREAD] FOR
      CHANNEL' to start the SQL thread which will use the value of
      sql_slave_skip_counter.
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_channel_sql_skip_counter"><code class="literal">ER_SLAVE_CHANNEL_SQL_SKIP_COUNTER</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_wrong_field_with_group_v2"></a>
      <a class="indexterm" name="idm46734186277712"></a>

      <a class="indexterm" name="idm46734186276672"></a>

      Error number: <code class="literal">3087</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_field_with_group_v2"><code class="literal">ER_WRONG_FIELD_WITH_GROUP_V2</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Expression #%u of %s is not in GROUP BY clause and
      contains nonaggregated column '%s' which is not functionally
      dependent on columns in GROUP BY clause; this is incompatible with
      sql_mode=only_full_group_by
    </p><p>
      <a class="link" href="error-handling.html#error_er_wrong_field_with_group_v2"><code class="literal">ER_WRONG_FIELD_WITH_GROUP_V2</code></a> was
      added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_mix_of_group_func_and_fields_v2"></a>
      <a class="indexterm" name="idm46734186268624"></a>

      <a class="indexterm" name="idm46734186267584"></a>

      Error number: <code class="literal">3088</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_mix_of_group_func_and_fields_v2"><code class="literal">ER_MIX_OF_GROUP_FUNC_AND_FIELDS_V2</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: In aggregated query without GROUP BY, expression #%u of
      %s contains nonaggregated column '%s'; this is incompatible with
      sql_mode=only_full_group_by
    </p><p>
      <a class="link" href="error-handling.html#error_er_mix_of_group_func_and_fields_v2"><code class="literal">ER_MIX_OF_GROUP_FUNC_AND_FIELDS_V2</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_warn_deprecated_sysvar_update"></a>
      <a class="indexterm" name="idm46734186259712"></a>

      <a class="indexterm" name="idm46734186258608"></a>

      Error number: <code class="literal">3089</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_deprecated_sysvar_update"><code class="literal">ER_WARN_DEPRECATED_SYSVAR_UPDATE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Updating '%s' is deprecated. It will be made read-only in
      a future release.
    </p><p>
      <a class="link" href="error-handling.html#error_er_warn_deprecated_sysvar_update"><code class="literal">ER_WARN_DEPRECATED_SYSVAR_UPDATE</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_warn_deprecated_sqlmode"></a>
      <a class="indexterm" name="idm46734186250928"></a>

      <a class="indexterm" name="idm46734186249888"></a>

      Error number: <code class="literal">3090</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_deprecated_sqlmode"><code class="literal">ER_WARN_DEPRECATED_SQLMODE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Changing sql mode '%s' is deprecated. It will be removed
      in a future release.
    </p><p>
      <a class="link" href="error-handling.html#error_er_warn_deprecated_sqlmode"><code class="literal">ER_WARN_DEPRECATED_SQLMODE</code></a> was
      added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_cannot_log_partial_drop_database_with_gtid"></a>
      <a class="indexterm" name="idm46734186242032"></a>

      <a class="indexterm" name="idm46734186240912"></a>

      Error number: <code class="literal">3091</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cannot_log_partial_drop_database_with_gtid"><code class="literal">ER_CANNOT_LOG_PARTIAL_DROP_DATABASE_WITH_GTID</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: DROP DATABASE failed; some tables may have been dropped
      but the database directory remains. The GTID has not been added to
      GTID_EXECUTED and the statement was not written to the binary log.
      Fix this as follows: (1) remove all files from the database
      directory %s; (2) SET GTID_NEXT='%s'; (3) DROP DATABASE `%s`.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cannot_log_partial_drop_database_with_gtid"><code class="literal">ER_CANNOT_LOG_PARTIAL_DROP_DATABASE_WITH_GTID</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_group_replication_configuration"></a>
      <a class="indexterm" name="idm46734186232768"></a>

      <a class="indexterm" name="idm46734186231728"></a>

      Error number: <code class="literal">3092</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_group_replication_configuration"><code class="literal">ER_GROUP_REPLICATION_CONFIGURATION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The server is not configured properly to be an active
      member of the group. Please see more details on error log.
    </p><p>
      <a class="link" href="error-handling.html#error_er_group_replication_configuration"><code class="literal">ER_GROUP_REPLICATION_CONFIGURATION</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_group_replication_running"></a>
      <a class="indexterm" name="idm46734186223888"></a>

      <a class="indexterm" name="idm46734186222848"></a>

      Error number: <code class="literal">3093</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_group_replication_running"><code class="literal">ER_GROUP_REPLICATION_RUNNING</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The START GROUP_REPLICATION command failed since the
      group is already running.
    </p><p>
      <a class="link" href="error-handling.html#error_er_group_replication_running"><code class="literal">ER_GROUP_REPLICATION_RUNNING</code></a> was
      added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_group_replication_applier_init_error"></a>
      <a class="indexterm" name="idm46734186215056"></a>

      <a class="indexterm" name="idm46734186214016"></a>

      Error number: <code class="literal">3094</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_group_replication_applier_init_error"><code class="literal">ER_GROUP_REPLICATION_APPLIER_INIT_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The START GROUP_REPLICATION command failed as the applier
      module failed to start.
    </p><p>
      <a class="link" href="error-handling.html#error_er_group_replication_applier_init_error"><code class="literal">ER_GROUP_REPLICATION_APPLIER_INIT_ERROR</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_group_replication_stop_applier_thread_timeout"></a>
      <a class="indexterm" name="idm46734186206160"></a>

      <a class="indexterm" name="idm46734186205040"></a>

      Error number: <code class="literal">3095</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_group_replication_stop_applier_thread_timeout"><code class="literal">ER_GROUP_REPLICATION_STOP_APPLIER_THREAD_TIMEOUT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The STOP GROUP_REPLICATION command execution is
      incomplete: The applier thread got the stop signal while it was
      busy. The applier thread will stop once the current task is
      complete.
    </p><p>
      <a class="link" href="error-handling.html#error_er_group_replication_stop_applier_thread_timeout"><code class="literal">ER_GROUP_REPLICATION_STOP_APPLIER_THREAD_TIMEOUT</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_group_replication_communication_layer_session_error"></a>
      <a class="indexterm" name="idm46734186196976"></a>

      <a class="indexterm" name="idm46734186195936"></a>

      Error number: <code class="literal">3096</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_group_replication_communication_layer_session_error"><code class="literal">ER_GROUP_REPLICATION_COMMUNICATION_LAYER_SESSION_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The START GROUP_REPLICATION command failed as there was
      an error when initializing the group communication layer.
    </p><p>
      <a class="link" href="error-handling.html#error_er_group_replication_communication_layer_session_error"><code class="literal">ER_GROUP_REPLICATION_COMMUNICATION_LAYER_SESSION_ERROR</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_group_replication_communication_layer_join_error"></a>
      <a class="indexterm" name="idm46734186187872"></a>

      <a class="indexterm" name="idm46734186186832"></a>

      Error number: <code class="literal">3097</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_group_replication_communication_layer_join_error"><code class="literal">ER_GROUP_REPLICATION_COMMUNICATION_LAYER_JOIN_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The START GROUP_REPLICATION command failed as there was
      an error when joining the communication group.
    </p><p>
      <a class="link" href="error-handling.html#error_er_group_replication_communication_layer_join_error"><code class="literal">ER_GROUP_REPLICATION_COMMUNICATION_LAYER_JOIN_ERROR</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_before_dml_validation_error"></a>
      <a class="indexterm" name="idm46734186178752"></a>

      <a class="indexterm" name="idm46734186177648"></a>

      Error number: <code class="literal">3098</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_before_dml_validation_error"><code class="literal">ER_BEFORE_DML_VALIDATION_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The table does not comply with the requirements by an
      external plugin.
    </p><p>
      <a class="link" href="error-handling.html#error_er_before_dml_validation_error"><code class="literal">ER_BEFORE_DML_VALIDATION_ERROR</code></a> was
      added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_prevents_variable_without_rbr"></a>
      <a class="indexterm" name="idm46734186169904"></a>

      <a class="indexterm" name="idm46734186168800"></a>

      Error number: <code class="literal">3099</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_prevents_variable_without_rbr"><code class="literal">ER_PREVENTS_VARIABLE_WITHOUT_RBR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot change the value of variable %s without binary log
      format as ROW.
    </p><p>
      <a class="link" href="replication.html#sysvar_transaction_write_set_extraction"><code class="literal">transaction_write_set_extraction</code></a>
      option value is set and
      <a class="link" href="replication.html#sysvar_binlog_format"><code class="literal">binlog_format</code></a> is not
      <code class="literal">ROW</code>.
    </p><p>
      <a class="link" href="error-handling.html#error_er_prevents_variable_without_rbr"><code class="literal">ER_PREVENTS_VARIABLE_WITHOUT_RBR</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_run_hook_error"></a>
      <a class="indexterm" name="idm46734186157504"></a>

      <a class="indexterm" name="idm46734186156448"></a>

      Error number: <code class="literal">3100</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_run_hook_error"><code class="literal">ER_RUN_HOOK_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Error on observer while running replication hook '%s'.
    </p><p>
      <a class="link" href="error-handling.html#error_er_run_hook_error"><code class="literal">ER_RUN_HOOK_ERROR</code></a> was added in
      5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_transaction_rollback_during_commit"></a>
      <a class="indexterm" name="idm46734186148736"></a>

      <a class="indexterm" name="idm46734186147696"></a>

      Error number: <code class="literal">3101</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_transaction_rollback_during_commit"><code class="literal">ER_TRANSACTION_ROLLBACK_DURING_COMMIT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Plugin instructed the server to rollback the current
      transaction.
    </p><p>
      When using Group Replication, this means that a transaction failed
      the group certification process, due to one or more members
      detecting a potential conflict, and was thus rolled back. See
      <a class="xref" href="group-replication.html" title="Chapter 17 Group Replication">Chapter 17, <i>Group Replication</i></a>.
    </p><p>
      <a class="link" href="error-handling.html#error_er_transaction_rollback_during_commit"><code class="literal">ER_TRANSACTION_ROLLBACK_DURING_COMMIT</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_generated_column_function_is_not_allowed"></a>
      <a class="indexterm" name="idm46734186138576"></a>

      <a class="indexterm" name="idm46734186137536"></a>

      Error number: <code class="literal">3102</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_generated_column_function_is_not_allowed"><code class="literal">ER_GENERATED_COLUMN_FUNCTION_IS_NOT_ALLOWED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Expression of generated column '%s' contains a disallowed
      function.
    </p><p>
      <a class="link" href="error-handling.html#error_er_generated_column_function_is_not_allowed"><code class="literal">ER_GENERATED_COLUMN_FUNCTION_IS_NOT_ALLOWED</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_key_based_on_generated_column"></a>
      <a class="indexterm" name="idm46734186129696"></a>

      <a class="indexterm" name="idm46734186128592"></a>

      Error number: <code class="literal">3103</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_key_based_on_generated_column"><code class="literal">ER_KEY_BASED_ON_GENERATED_COLUMN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Key/Index cannot be defined on a virtual generated
      column.
    </p><p>
      <a class="link" href="error-handling.html#error_er_key_based_on_generated_column"><code class="literal">ER_KEY_BASED_ON_GENERATED_COLUMN</code></a>
      was added in 5.7.6, removed after 5.7.7.
    </p></li><li class="listitem"><p><a name="error_er_unsupported_alter_inplace_on_virtual_column"></a>
      <a class="indexterm" name="idm46734186120800"></a>

      <a class="indexterm" name="idm46734186119760"></a>

      Error number: <code class="literal">3103</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unsupported_alter_inplace_on_virtual_column"><code class="literal">ER_UNSUPPORTED_ALTER_INPLACE_ON_VIRTUAL_COLUMN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: INPLACE ADD or DROP of virtual columns cannot be combined
      with other ALTER TABLE actions
    </p><p>
      <a class="link" href="error-handling.html#error_er_unsupported_alter_inplace_on_virtual_column"><code class="literal">ER_UNSUPPORTED_ALTER_INPLACE_ON_VIRTUAL_COLUMN</code></a>
      was added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_wrong_fk_option_for_generated_column"></a>
      <a class="indexterm" name="idm46734186111920"></a>

      <a class="indexterm" name="idm46734186110880"></a>

      Error number: <code class="literal">3104</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_fk_option_for_generated_column"><code class="literal">ER_WRONG_FK_OPTION_FOR_GENERATED_COLUMN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot define foreign key with %s clause on a generated
      column.
    </p><p>
      <a class="link" href="error-handling.html#error_er_wrong_fk_option_for_generated_column"><code class="literal">ER_WRONG_FK_OPTION_FOR_GENERATED_COLUMN</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_non_default_value_for_generated_column"></a>
      <a class="indexterm" name="idm46734186102976"></a>

      <a class="indexterm" name="idm46734186101936"></a>

      Error number: <code class="literal">3105</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_non_default_value_for_generated_column"><code class="literal">ER_NON_DEFAULT_VALUE_FOR_GENERATED_COLUMN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The value specified for generated column '%s' in table
      '%s' is not allowed.
    </p><p>
      <a class="link" href="error-handling.html#error_er_non_default_value_for_generated_column"><code class="literal">ER_NON_DEFAULT_VALUE_FOR_GENERATED_COLUMN</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_unsupported_action_on_generated_column"></a>
      <a class="indexterm" name="idm46734186093984"></a>

      <a class="indexterm" name="idm46734186092944"></a>

      Error number: <code class="literal">3106</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unsupported_action_on_generated_column"><code class="literal">ER_UNSUPPORTED_ACTION_ON_GENERATED_COLUMN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: '%s' is not supported for generated columns.
    </p><p>
      <a class="link" href="error-handling.html#error_er_unsupported_action_on_generated_column"><code class="literal">ER_UNSUPPORTED_ACTION_ON_GENERATED_COLUMN</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_generated_column_non_prior"></a>
      <a class="indexterm" name="idm46734186085008"></a>

      <a class="indexterm" name="idm46734186083904"></a>

      Error number: <code class="literal">3107</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_generated_column_non_prior"><code class="literal">ER_GENERATED_COLUMN_NON_PRIOR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Generated column can refer only to generated columns
      defined prior to it.
    </p><p>
      To address this issue, change the table definition to define each
      generated column later than any generated columns to which it
      refers.
    </p><p>
      <a class="link" href="error-handling.html#error_er_generated_column_non_prior"><code class="literal">ER_GENERATED_COLUMN_NON_PRIOR</code></a> was
      added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_dependent_by_generated_column"></a>
      <a class="indexterm" name="idm46734186075536"></a>

      <a class="indexterm" name="idm46734186074432"></a>

      Error number: <code class="literal">3108</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_dependent_by_generated_column"><code class="literal">ER_DEPENDENT_BY_GENERATED_COLUMN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Column '%s' has a generated column dependency.
    </p><p>
      You cannot drop or rename a generated column if another column
      refers to it. You must either drop those columns as well, or
      redefine them not to refer to the generated column.
    </p><p>
      <a class="link" href="error-handling.html#error_er_dependent_by_generated_column"><code class="literal">ER_DEPENDENT_BY_GENERATED_COLUMN</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_generated_column_ref_auto_inc"></a>
      <a class="indexterm" name="idm46734186066128"></a>

      <a class="indexterm" name="idm46734186065024"></a>

      Error number: <code class="literal">3109</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_generated_column_ref_auto_inc"><code class="literal">ER_GENERATED_COLUMN_REF_AUTO_INC</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Generated column '%s' cannot refer to auto-increment
      column.
    </p><p>
      <a class="link" href="error-handling.html#error_er_generated_column_ref_auto_inc"><code class="literal">ER_GENERATED_COLUMN_REF_AUTO_INC</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_feature_not_available"></a>
      <a class="indexterm" name="idm46734186057296"></a>

      <a class="indexterm" name="idm46734186056256"></a>

      Error number: <code class="literal">3110</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_feature_not_available"><code class="literal">ER_FEATURE_NOT_AVAILABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The '%s' feature is not available; you need to remove
      '%s' or use MySQL built with '%s'
    </p><p>
      <a class="link" href="error-handling.html#error_er_feature_not_available"><code class="literal">ER_FEATURE_NOT_AVAILABLE</code></a> was added
      in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_cant_set_gtid_mode"></a>
      <a class="indexterm" name="idm46734186048384"></a>

      <a class="indexterm" name="idm46734186047344"></a>

      Error number: <code class="literal">3111</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_set_gtid_mode"><code class="literal">ER_CANT_SET_GTID_MODE</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: SET @@GLOBAL.GTID_MODE = %s is not allowed because %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cant_set_gtid_mode"><code class="literal">ER_CANT_SET_GTID_MODE</code></a> was added in
      5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_cant_use_auto_position_with_gtid_mode_off"></a>
      <a class="indexterm" name="idm46734186039504"></a>

      <a class="indexterm" name="idm46734186038464"></a>

      Error number: <code class="literal">3112</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_use_auto_position_with_gtid_mode_off"><code class="literal">ER_CANT_USE_AUTO_POSITION_WITH_GTID_MODE_OFF</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The replication receiver thread%s cannot start in
      AUTO_POSITION mode: this server uses @@GLOBAL.GTID_MODE = OFF.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cant_use_auto_position_with_gtid_mode_off"><code class="literal">ER_CANT_USE_AUTO_POSITION_WITH_GTID_MODE_OFF</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_cant_replicate_anonymous_with_auto_position"></a>
      <a class="indexterm" name="idm46734186030464"></a>

      <a class="indexterm" name="idm46734186029344"></a>

      Error number: <code class="literal">3113</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_replicate_anonymous_with_auto_position"><code class="literal">ER_CANT_REPLICATE_ANONYMOUS_WITH_AUTO_POSITION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot replicate anonymous transaction when AUTO_POSITION
      = 1, at file %s, position %lld.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cant_replicate_anonymous_with_auto_position"><code class="literal">ER_CANT_REPLICATE_ANONYMOUS_WITH_AUTO_POSITION</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_cant_replicate_anonymous_with_gtid_mode_on"></a>
      <a class="indexterm" name="idm46734186021504"></a>

      <a class="indexterm" name="idm46734186020384"></a>

      Error number: <code class="literal">3114</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_replicate_anonymous_with_gtid_mode_on"><code class="literal">ER_CANT_REPLICATE_ANONYMOUS_WITH_GTID_MODE_ON</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot replicate anonymous transaction when
      @@GLOBAL.GTID_MODE = ON, at file %s, position %lld.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cant_replicate_anonymous_with_gtid_mode_on"><code class="literal">ER_CANT_REPLICATE_ANONYMOUS_WITH_GTID_MODE_ON</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_cant_replicate_gtid_with_gtid_mode_off"></a>
      <a class="indexterm" name="idm46734186012464"></a>

      <a class="indexterm" name="idm46734186011424"></a>

      Error number: <code class="literal">3115</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_replicate_gtid_with_gtid_mode_off"><code class="literal">ER_CANT_REPLICATE_GTID_WITH_GTID_MODE_OFF</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot replicate GTID-transaction when @@GLOBAL.GTID_MODE
      = OFF, at file %s, position %lld.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cant_replicate_gtid_with_gtid_mode_off"><code class="literal">ER_CANT_REPLICATE_GTID_WITH_GTID_MODE_OFF</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_cant_set_enforce_gtid_consistency_on_with_ongoing_gtid_violating_transactions"></a>
      <a class="indexterm" name="idm46734186003408"></a>

      <a class="indexterm" name="idm46734186002256"></a>

      Error number: <code class="literal">3116</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_set_enforce_gtid_consistency_on_with_ongoing_gtid_violating_transactions"><code class="literal">ER_CANT_SET_ENFORCE_GTID_CONSISTENCY_ON_WITH_ONGOING_GTID_VIOLATING_TRANSACTIONS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot set ENFORCE_GTID_CONSISTENCY = ON because there
      are ongoing transactions that violate GTID consistency.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cant_set_enforce_gtid_consistency_on_with_ongoing_gtid_violating_transactions"><code class="literal">ER_CANT_SET_ENFORCE_GTID_CONSISTENCY_ON_WITH_ONGOING_GTID_VIOLATING_TRANSACTIONS</code></a>
      is renamed to
      <code class="literal">ER_CANT_ENFORCE_GTID_CONSISTENCY_WITH_ONGOING_GTID_VIOLATING_TX</code>
      in MySQL 8.0.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cant_set_enforce_gtid_consistency_on_with_ongoing_gtid_violating_transactions"><code class="literal">ER_CANT_SET_ENFORCE_GTID_CONSISTENCY_ON_WITH_ONGOING_GTID_VIOLATING_TRANSACTIONS</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_set_enforce_gtid_consistency_warn_with_ongoing_gtid_violating_transactions"></a>
      <a class="indexterm" name="idm46734185991424"></a>

      <a class="indexterm" name="idm46734185990272"></a>

      Error number: <code class="literal">3117</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_set_enforce_gtid_consistency_warn_with_ongoing_gtid_violating_transactions"><code class="literal">ER_SET_ENFORCE_GTID_CONSISTENCY_WARN_WITH_ONGOING_GTID_VIOLATING_TRANSACTIONS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: There are ongoing transactions that violate GTID
      consistency.
    </p><p>
      <a class="link" href="error-handling.html#error_er_set_enforce_gtid_consistency_warn_with_ongoing_gtid_violating_transactions"><code class="literal">ER_SET_ENFORCE_GTID_CONSISTENCY_WARN_WITH_ONGOING_GTID_VIOLATING_TRANSACTIONS</code></a>
      is renamed to
      <code class="literal">ER_ENFORCE_GTID_CONSISTENCY_WARN_WITH_ONGOING_GTID_VIOLATING_TX</code>
      in MySQL 8.0.
    </p><p>
      <a class="link" href="error-handling.html#error_er_set_enforce_gtid_consistency_warn_with_ongoing_gtid_violating_transactions"><code class="literal">ER_SET_ENFORCE_GTID_CONSISTENCY_WARN_WITH_ONGOING_GTID_VIOLATING_TRANSACTIONS</code></a>
      was added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_account_has_been_locked"></a>
      <a class="indexterm" name="idm46734185979744"></a>

      <a class="indexterm" name="idm46734185978704"></a>

      Error number: <code class="literal">3118</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_account_has_been_locked"><code class="literal">ER_ACCOUNT_HAS_BEEN_LOCKED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Access denied for user '%s'@'%s'. Account is locked.
    </p><p>
      The account was locked with
      <a class="link" href="sql-statements.html#create-user" title="13.7.1.2 CREATE USER Statement"><code class="literal">CREATE USER ...
      ACCOUNT LOCK</code></a> or
      <a class="link" href="sql-statements.html#alter-user" title="13.7.1.1 ALTER USER Statement"><code class="literal">ALTER USER ... ACCOUNT
      LOCK</code></a>. An administrator can unlock it with
      <a class="link" href="sql-statements.html#alter-user" title="13.7.1.1 ALTER USER Statement"><code class="literal">ALTER USER ... ACCOUNT
      UNLOCK</code></a>.
    </p><p>
      <a class="link" href="error-handling.html#error_er_account_has_been_locked"><code class="literal">ER_ACCOUNT_HAS_BEEN_LOCKED</code></a> was
      added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_wrong_tablespace_name"></a>
      <a class="indexterm" name="idm46734185966768"></a>

      <a class="indexterm" name="idm46734185965728"></a>

      Error number: <code class="literal">3119</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_tablespace_name"><code class="literal">ER_WRONG_TABLESPACE_NAME</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Incorrect tablespace name `%s`
    </p><p>
      <a class="link" href="error-handling.html#error_er_wrong_tablespace_name"><code class="literal">ER_WRONG_TABLESPACE_NAME</code></a> was added
      in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_tablespace_is_not_empty"></a>
      <a class="indexterm" name="idm46734185957984"></a>

      <a class="indexterm" name="idm46734185956944"></a>

      Error number: <code class="literal">3120</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_tablespace_is_not_empty"><code class="literal">ER_TABLESPACE_IS_NOT_EMPTY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Tablespace `%s` is not empty.
    </p><p>
      <a class="link" href="error-handling.html#error_er_tablespace_is_not_empty"><code class="literal">ER_TABLESPACE_IS_NOT_EMPTY</code></a> was
      added in 5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_wrong_file_name"></a>
      <a class="indexterm" name="idm46734185949264"></a>

      <a class="indexterm" name="idm46734185948224"></a>

      Error number: <code class="literal">3121</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_wrong_file_name"><code class="literal">ER_WRONG_FILE_NAME</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Incorrect File Name '%s'.
    </p><p>
      <a class="link" href="error-handling.html#error_er_wrong_file_name"><code class="literal">ER_WRONG_FILE_NAME</code></a> was added in
      5.7.6.
    </p></li><li class="listitem"><p><a name="error_er_boost_geometry_inconsistent_turns_exception"></a>
      <a class="indexterm" name="idm46734185940480"></a>

      <a class="indexterm" name="idm46734185939360"></a>

      Error number: <code class="literal">3122</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_boost_geometry_inconsistent_turns_exception"><code class="literal">ER_BOOST_GEOMETRY_INCONSISTENT_TURNS_EXCEPTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Inconsistent intersection points.
    </p><p>
      <a class="link" href="error-handling.html#error_er_boost_geometry_inconsistent_turns_exception"><code class="literal">ER_BOOST_GEOMETRY_INCONSISTENT_TURNS_EXCEPTION</code></a>
      was added in 5.7.7.
    </p></li><li class="listitem"><p><a name="error_er_warn_optimizer_hint_syntax_error"></a>
      <a class="indexterm" name="idm46734185931520"></a>

      <a class="indexterm" name="idm46734185930480"></a>

      Error number: <code class="literal">3123</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_optimizer_hint_syntax_error"><code class="literal">ER_WARN_OPTIMIZER_HINT_SYNTAX_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Optimizer hint syntax error
    </p><p>
      <a class="link" href="error-handling.html#error_er_warn_optimizer_hint_syntax_error"><code class="literal">ER_WARN_OPTIMIZER_HINT_SYNTAX_ERROR</code></a>
      was added in 5.7.7.
    </p></li><li class="listitem"><p><a name="error_er_warn_bad_max_execution_time"></a>
      <a class="indexterm" name="idm46734185922672"></a>

      <a class="indexterm" name="idm46734185921568"></a>

      Error number: <code class="literal">3124</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_bad_max_execution_time"><code class="literal">ER_WARN_BAD_MAX_EXECUTION_TIME</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Unsupported MAX_EXECUTION_TIME
    </p><p>
      <a class="link" href="error-handling.html#error_er_warn_bad_max_execution_time"><code class="literal">ER_WARN_BAD_MAX_EXECUTION_TIME</code></a> was
      added in 5.7.7.
    </p></li><li class="listitem"><p><a name="error_er_warn_unsupported_max_execution_time"></a>
      <a class="indexterm" name="idm46734185913888"></a>

      <a class="indexterm" name="idm46734185912848"></a>

      Error number: <code class="literal">3125</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_unsupported_max_execution_time"><code class="literal">ER_WARN_UNSUPPORTED_MAX_EXECUTION_TIME</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: MAX_EXECUTION_TIME hint is supported by top-level
      standalone SELECT statements only
    </p><p>
      The <code class="literal">MAX_EXECUTION_TIME</code> optimizer hint is
      supported only for <a class="link" href="sql-statements.html#select" title="13.2.9 SELECT Statement"><code class="literal">SELECT</code></a>
      statements.
    </p><p>
      <a class="link" href="error-handling.html#error_er_warn_unsupported_max_execution_time"><code class="literal">ER_WARN_UNSUPPORTED_MAX_EXECUTION_TIME</code></a>
      was added in 5.7.7.
    </p></li><li class="listitem"><p><a name="error_er_warn_conflicting_hint"></a>
      <a class="indexterm" name="idm46734185902576"></a>

      <a class="indexterm" name="idm46734185901536"></a>

      Error number: <code class="literal">3126</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_conflicting_hint"><code class="literal">ER_WARN_CONFLICTING_HINT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Hint %s is ignored as conflicting/duplicated
    </p><p>
      <a class="link" href="error-handling.html#error_er_warn_conflicting_hint"><code class="literal">ER_WARN_CONFLICTING_HINT</code></a> was added
      in 5.7.7.
    </p></li><li class="listitem"><p><a name="error_er_warn_unknown_qb_name"></a>
      <a class="indexterm" name="idm46734185893712"></a>

      <a class="indexterm" name="idm46734185892672"></a>

      Error number: <code class="literal">3127</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_unknown_qb_name"><code class="literal">ER_WARN_UNKNOWN_QB_NAME</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Query block name %s is not found for %s hint
    </p><p>
      <a class="link" href="error-handling.html#error_er_warn_unknown_qb_name"><code class="literal">ER_WARN_UNKNOWN_QB_NAME</code></a> was added
      in 5.7.7.
    </p></li><li class="listitem"><p><a name="error_er_unresolved_hint_name"></a>
      <a class="indexterm" name="idm46734185885024"></a>

      <a class="indexterm" name="idm46734185883984"></a>

      Error number: <code class="literal">3128</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unresolved_hint_name"><code class="literal">ER_UNRESOLVED_HINT_NAME</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Unresolved name %s for %s hint
    </p><p>
      <a class="link" href="error-handling.html#error_er_unresolved_hint_name"><code class="literal">ER_UNRESOLVED_HINT_NAME</code></a> was added
      in 5.7.7.
    </p></li><li class="listitem"><p><a name="error_er_warn_deprecated_sqlmode_unset"></a>
      <a class="indexterm" name="idm46734185876352"></a>

      <a class="indexterm" name="idm46734185875248"></a>

      Error number: <code class="literal">3129</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_deprecated_sqlmode_unset"><code class="literal">ER_WARN_DEPRECATED_SQLMODE_UNSET</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Unsetting sql mode '%s' is deprecated. It will be made
      read-only in a future release.
    </p><p>
      <a class="link" href="error-handling.html#error_er_warn_deprecated_sqlmode_unset"><code class="literal">ER_WARN_DEPRECATED_SQLMODE_UNSET</code></a>
      was added in 5.7.7, removed after 5.7.7.
    </p></li><li class="listitem"><p><a name="error_er_warn_on_modifying_gtid_executed_table"></a>
      <a class="indexterm" name="idm46734185867488"></a>

      <a class="indexterm" name="idm46734185866448"></a>

      Error number: <code class="literal">3129</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_on_modifying_gtid_executed_table"><code class="literal">ER_WARN_ON_MODIFYING_GTID_EXECUTED_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Please do not modify the %s table. This is a mysql
      internal system table to store GTIDs for committed transactions.
      Modifying it can lead to an inconsistent GTID state.
    </p><p>
      <a class="link" href="error-handling.html#error_er_warn_on_modifying_gtid_executed_table"><code class="literal">ER_WARN_ON_MODIFYING_GTID_EXECUTED_TABLE</code></a>
      was added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_pluggable_protocol_command_not_supported"></a>
      <a class="indexterm" name="idm46734185858384"></a>

      <a class="indexterm" name="idm46734185857344"></a>

      Error number: <code class="literal">3130</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_pluggable_protocol_command_not_supported"><code class="literal">ER_PLUGGABLE_PROTOCOL_COMMAND_NOT_SUPPORTED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Command not supported by pluggable protocols
    </p><p>
      <a class="link" href="error-handling.html#error_er_pluggable_protocol_command_not_supported"><code class="literal">ER_PLUGGABLE_PROTOCOL_COMMAND_NOT_SUPPORTED</code></a>
      was added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_locking_service_wrong_name"></a>
      <a class="indexterm" name="idm46734185849584"></a>

      <a class="indexterm" name="idm46734185848480"></a>

      Error number: <code class="literal">3131</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_locking_service_wrong_name"><code class="literal">ER_LOCKING_SERVICE_WRONG_NAME</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Incorrect locking service lock name '%s'.
    </p><p>
      A locking service name was specified as <code class="literal">NULL</code>,
      the empty string, or a string longer than 64 characters. Namespace
      and lock names must be non-<code class="literal">NULL</code>, nonempty, and
      no more than 64 characters long.
    </p><p>
      <a class="link" href="error-handling.html#error_er_locking_service_wrong_name"><code class="literal">ER_LOCKING_SERVICE_WRONG_NAME</code></a> was
      added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_locking_service_deadlock"></a>
      <a class="indexterm" name="idm46734185838912"></a>

      <a class="indexterm" name="idm46734185837872"></a>

      Error number: <code class="literal">3132</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_locking_service_deadlock"><code class="literal">ER_LOCKING_SERVICE_DEADLOCK</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Deadlock found when trying to get locking service lock;
      try releasing locks and restarting lock acquisition.
    </p><p>
      <a class="link" href="error-handling.html#error_er_locking_service_deadlock"><code class="literal">ER_LOCKING_SERVICE_DEADLOCK</code></a> was
      added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_locking_service_timeout"></a>
      <a class="indexterm" name="idm46734185830224"></a>

      <a class="indexterm" name="idm46734185829184"></a>

      Error number: <code class="literal">3133</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_locking_service_timeout"><code class="literal">ER_LOCKING_SERVICE_TIMEOUT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Service lock wait timeout exceeded.
    </p><p>
      <a class="link" href="error-handling.html#error_er_locking_service_timeout"><code class="literal">ER_LOCKING_SERVICE_TIMEOUT</code></a> was
      added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_gis_max_points_in_geometry_overflowed"></a>
      <a class="indexterm" name="idm46734185821504"></a>

      <a class="indexterm" name="idm46734185820464"></a>

      Error number: <code class="literal">3134</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_gis_max_points_in_geometry_overflowed"><code class="literal">ER_GIS_MAX_POINTS_IN_GEOMETRY_OVERFLOWED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Parameter %s exceeds the maximum number of points in a
      geometry (%lu) in function %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_gis_max_points_in_geometry_overflowed"><code class="literal">ER_GIS_MAX_POINTS_IN_GEOMETRY_OVERFLOWED</code></a>
      was added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_sql_mode_merged"></a>
      <a class="indexterm" name="idm46734185812592"></a>

      <a class="indexterm" name="idm46734185811552"></a>

      Error number: <code class="literal">3135</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_sql_mode_merged"><code class="literal">ER_SQL_MODE_MERGED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: 'NO_ZERO_DATE', 'NO_ZERO_IN_DATE' and
      'ERROR_FOR_DIVISION_BY_ZERO' sql modes should be used with strict
      mode. They will be merged with strict mode in a future release.
    </p><p>
      <a class="link" href="error-handling.html#error_er_sql_mode_merged"><code class="literal">ER_SQL_MODE_MERGED</code></a> was added in
      5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_vtoken_plugin_token_mismatch"></a>
      <a class="indexterm" name="idm46734185803808"></a>

      <a class="indexterm" name="idm46734185802704"></a>

      Error number: <code class="literal">3136</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_vtoken_plugin_token_mismatch"><code class="literal">ER_VTOKEN_PLUGIN_TOKEN_MISMATCH</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Version token mismatch for %.*s. Correct value %.*s
    </p><p>
      The client has set its
      <a class="link" href="server-administration.html#sysvar_version_tokens_session"><code class="literal">version_tokens_session</code></a> system
      variable to the list of tokens it requires the server to match,
      but the server token list has at least one matching token name
      that has a value different from what the client requires. See
      <a class="xref" href="server-administration.html#version-tokens" title="5.5.5 Version Tokens">Section 5.5.5, “Version Tokens”</a>.
    </p><p>
      <a class="link" href="error-handling.html#error_er_vtoken_plugin_token_mismatch"><code class="literal">ER_VTOKEN_PLUGIN_TOKEN_MISMATCH</code></a>
      was added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_vtoken_plugin_token_not_found"></a>
      <a class="indexterm" name="idm46734185792576"></a>

      <a class="indexterm" name="idm46734185791472"></a>

      Error number: <code class="literal">3137</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_vtoken_plugin_token_not_found"><code class="literal">ER_VTOKEN_PLUGIN_TOKEN_NOT_FOUND</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Version token %.*s not found.
    </p><p>
      The client has set its
      <a class="link" href="server-administration.html#sysvar_version_tokens_session"><code class="literal">version_tokens_session</code></a> system
      variable to the list of tokens it requires the server to match,
      but the server token list is missing at least one of those tokens.
      See <a class="xref" href="server-administration.html#version-tokens" title="5.5.5 Version Tokens">Section 5.5.5, “Version Tokens”</a>.
    </p><p>
      <a class="link" href="error-handling.html#error_er_vtoken_plugin_token_not_found"><code class="literal">ER_VTOKEN_PLUGIN_TOKEN_NOT_FOUND</code></a>
      was added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_cant_set_variable_when_owning_gtid"></a>
      <a class="indexterm" name="idm46734185781344"></a>

      <a class="indexterm" name="idm46734185780304"></a>

      Error number: <code class="literal">3138</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_set_variable_when_owning_gtid"><code class="literal">ER_CANT_SET_VARIABLE_WHEN_OWNING_GTID</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Variable %s cannot be changed by a client that owns a
      GTID. The client owns %s. Ownership is released on COMMIT or
      ROLLBACK.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cant_set_variable_when_owning_gtid"><code class="literal">ER_CANT_SET_VARIABLE_WHEN_OWNING_GTID</code></a>
      was added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_slave_channel_operation_not_allowed"></a>
      <a class="indexterm" name="idm46734185772400"></a>

      <a class="indexterm" name="idm46734185771360"></a>

      Error number: <code class="literal">3139</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_slave_channel_operation_not_allowed"><code class="literal">ER_SLAVE_CHANNEL_OPERATION_NOT_ALLOWED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: %s cannot be performed on channel '%s'.
    </p><p>
      <a class="link" href="error-handling.html#error_er_slave_channel_operation_not_allowed"><code class="literal">ER_SLAVE_CHANNEL_OPERATION_NOT_ALLOWED</code></a>
      was added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_invalid_json_text"></a>
      <a class="indexterm" name="idm46734185763472"></a>

      <a class="indexterm" name="idm46734185762432"></a>

      Error number: <code class="literal">3140</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_json_text"><code class="literal">ER_INVALID_JSON_TEXT</code></a>; SQLSTATE:
      <code class="literal">22032</code>
    </p><p>
      Message: Invalid JSON text: "%s" at position %u in value for
      column '%s'.
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_json_text"><code class="literal">ER_INVALID_JSON_TEXT</code></a> was added in
      5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_invalid_json_text_in_param"></a>
      <a class="indexterm" name="idm46734185754752"></a>

      <a class="indexterm" name="idm46734185753648"></a>

      Error number: <code class="literal">3141</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_json_text_in_param"><code class="literal">ER_INVALID_JSON_TEXT_IN_PARAM</code></a>;
      SQLSTATE: <code class="literal">22032</code>
    </p><p>
      Message: Invalid JSON text in argument %u to function %s: "%s" at
      position %u.%s
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_json_text_in_param"><code class="literal">ER_INVALID_JSON_TEXT_IN_PARAM</code></a> was
      added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_invalid_json_binary_data"></a>
      <a class="indexterm" name="idm46734185745904"></a>

      <a class="indexterm" name="idm46734185744864"></a>

      Error number: <code class="literal">3142</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_json_binary_data"><code class="literal">ER_INVALID_JSON_BINARY_DATA</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The JSON binary value contains invalid data.
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_json_binary_data"><code class="literal">ER_INVALID_JSON_BINARY_DATA</code></a> was
      added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_invalid_json_path"></a>
      <a class="indexterm" name="idm46734185737168"></a>

      <a class="indexterm" name="idm46734185736128"></a>

      Error number: <code class="literal">3143</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_json_path"><code class="literal">ER_INVALID_JSON_PATH</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: Invalid JSON path expression. The error is around
      character position %u.%s
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_json_path"><code class="literal">ER_INVALID_JSON_PATH</code></a> was added in
      5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_invalid_json_charset"></a>
      <a class="indexterm" name="idm46734185728320"></a>

      <a class="indexterm" name="idm46734185727280"></a>

      Error number: <code class="literal">3144</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_json_charset"><code class="literal">ER_INVALID_JSON_CHARSET</code></a>; SQLSTATE:
      <code class="literal">22032</code>
    </p><p>
      Message: Cannot create a JSON value from a string with CHARACTER
      SET '%s'.
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_json_charset"><code class="literal">ER_INVALID_JSON_CHARSET</code></a> was added
      in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_invalid_json_charset_in_function"></a>
      <a class="indexterm" name="idm46734185719552"></a>

      <a class="indexterm" name="idm46734185718512"></a>

      Error number: <code class="literal">3145</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_json_charset_in_function"><code class="literal">ER_INVALID_JSON_CHARSET_IN_FUNCTION</code></a>;
      SQLSTATE: <code class="literal">22032</code>
    </p><p>
      Message: Invalid JSON character data provided to function %s:
      '%s'; utf8 is required.
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_json_charset_in_function"><code class="literal">ER_INVALID_JSON_CHARSET_IN_FUNCTION</code></a>
      was added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_invalid_type_for_json"></a>
      <a class="indexterm" name="idm46734185710720"></a>

      <a class="indexterm" name="idm46734185709680"></a>

      Error number: <code class="literal">3146</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_type_for_json"><code class="literal">ER_INVALID_TYPE_FOR_JSON</code></a>;
      SQLSTATE: <code class="literal">22032</code>
    </p><p>
      Message: Invalid data type for JSON data in argument %u to
      function %s; a JSON string or JSON type is required.
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_type_for_json"><code class="literal">ER_INVALID_TYPE_FOR_JSON</code></a> was added
      in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_invalid_cast_to_json"></a>
      <a class="indexterm" name="idm46734185701920"></a>

      <a class="indexterm" name="idm46734185700880"></a>

      Error number: <code class="literal">3147</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_cast_to_json"><code class="literal">ER_INVALID_CAST_TO_JSON</code></a>; SQLSTATE:
      <code class="literal">22032</code>
    </p><p>
      Message: Cannot CAST value to JSON.
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_cast_to_json"><code class="literal">ER_INVALID_CAST_TO_JSON</code></a> was added
      in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_invalid_json_path_charset"></a>
      <a class="indexterm" name="idm46734185693184"></a>

      <a class="indexterm" name="idm46734185692144"></a>

      Error number: <code class="literal">3148</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_json_path_charset"><code class="literal">ER_INVALID_JSON_PATH_CHARSET</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: A path expression must be encoded in the utf8 character
      set. The path expression '%s' is encoded in character set '%s'.
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_json_path_charset"><code class="literal">ER_INVALID_JSON_PATH_CHARSET</code></a> was
      added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_invalid_json_path_wildcard"></a>
      <a class="indexterm" name="idm46734185684352"></a>

      <a class="indexterm" name="idm46734185683248"></a>

      Error number: <code class="literal">3149</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_json_path_wildcard"><code class="literal">ER_INVALID_JSON_PATH_WILDCARD</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: In this situation, path expressions may not contain the *
      and ** tokens.
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_json_path_wildcard"><code class="literal">ER_INVALID_JSON_PATH_WILDCARD</code></a> was
      added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_json_value_too_big"></a>
      <a class="indexterm" name="idm46734185675504"></a>

      <a class="indexterm" name="idm46734185674464"></a>

      Error number: <code class="literal">3150</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_json_value_too_big"><code class="literal">ER_JSON_VALUE_TOO_BIG</code></a>; SQLSTATE:
      <code class="literal">22032</code>
    </p><p>
      Message: The JSON value is too big to be stored in a JSON column.
    </p><p>
      <a class="link" href="error-handling.html#error_er_json_value_too_big"><code class="literal">ER_JSON_VALUE_TOO_BIG</code></a> was added in
      5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_json_key_too_big"></a>
      <a class="indexterm" name="idm46734185666672"></a>

      <a class="indexterm" name="idm46734185665632"></a>

      Error number: <code class="literal">3151</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_json_key_too_big"><code class="literal">ER_JSON_KEY_TOO_BIG</code></a>; SQLSTATE:
      <code class="literal">22032</code>
    </p><p>
      Message: The JSON object contains a key name that is too long.
    </p><p>
      <a class="link" href="error-handling.html#error_er_json_key_too_big"><code class="literal">ER_JSON_KEY_TOO_BIG</code></a> was added in
      5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_json_used_as_key"></a>
      <a class="indexterm" name="idm46734185657968"></a>

      <a class="indexterm" name="idm46734185656928"></a>

      Error number: <code class="literal">3152</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_json_used_as_key"><code class="literal">ER_JSON_USED_AS_KEY</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: JSON column '%s' cannot be used in key specification.
    </p><p>
      <a class="link" href="error-handling.html#error_er_json_used_as_key"><code class="literal">ER_JSON_USED_AS_KEY</code></a> was added in
      5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_json_vacuous_path"></a>
      <a class="indexterm" name="idm46734185649200"></a>

      <a class="indexterm" name="idm46734185648160"></a>

      Error number: <code class="literal">3153</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_json_vacuous_path"><code class="literal">ER_JSON_VACUOUS_PATH</code></a>; SQLSTATE:
      <code class="literal">42000</code>
    </p><p>
      Message: The path expression '$' is not allowed in this context.
    </p><p>
      <a class="link" href="error-handling.html#error_er_json_vacuous_path"><code class="literal">ER_JSON_VACUOUS_PATH</code></a> was added in
      5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_json_bad_one_or_all_arg"></a>
      <a class="indexterm" name="idm46734185640432"></a>

      <a class="indexterm" name="idm46734185639392"></a>

      Error number: <code class="literal">3154</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_json_bad_one_or_all_arg"><code class="literal">ER_JSON_BAD_ONE_OR_ALL_ARG</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: The oneOrAll argument to %s may take these values: 'one'
      or 'all'.
    </p><p>
      <a class="link" href="error-handling.html#error_er_json_bad_one_or_all_arg"><code class="literal">ER_JSON_BAD_ONE_OR_ALL_ARG</code></a> was
      added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_numeric_json_value_out_of_range"></a>
      <a class="indexterm" name="idm46734185631488"></a>

      <a class="indexterm" name="idm46734185630448"></a>

      Error number: <code class="literal">3155</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_numeric_json_value_out_of_range"><code class="literal">ER_NUMERIC_JSON_VALUE_OUT_OF_RANGE</code></a>;
      SQLSTATE: <code class="literal">22003</code>
    </p><p>
      Message: Out of range JSON value for CAST to %s%s from column %s
      at row %ld
    </p><p>
      <a class="link" href="error-handling.html#error_er_numeric_json_value_out_of_range"><code class="literal">ER_NUMERIC_JSON_VALUE_OUT_OF_RANGE</code></a>
      was added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_invalid_json_value_for_cast"></a>
      <a class="indexterm" name="idm46734185622656"></a>

      <a class="indexterm" name="idm46734185621552"></a>

      Error number: <code class="literal">3156</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_json_value_for_cast"><code class="literal">ER_INVALID_JSON_VALUE_FOR_CAST</code></a>;
      SQLSTATE: <code class="literal">22018</code>
    </p><p>
      Message: Invalid JSON value for CAST to %s%s from column %s at row
      %ld
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_json_value_for_cast"><code class="literal">ER_INVALID_JSON_VALUE_FOR_CAST</code></a> was
      added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_json_document_too_deep"></a>
      <a class="indexterm" name="idm46734185613808"></a>

      <a class="indexterm" name="idm46734185612768"></a>

      Error number: <code class="literal">3157</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_json_document_too_deep"><code class="literal">ER_JSON_DOCUMENT_TOO_DEEP</code></a>;
      SQLSTATE: <code class="literal">22032</code>
    </p><p>
      Message: The JSON document exceeds the maximum depth.
    </p><p>
      <a class="link" href="error-handling.html#error_er_json_document_too_deep"><code class="literal">ER_JSON_DOCUMENT_TOO_DEEP</code></a> was
      added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_json_document_null_key"></a>
      <a class="indexterm" name="idm46734185605072"></a>

      <a class="indexterm" name="idm46734185604032"></a>

      Error number: <code class="literal">3158</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_json_document_null_key"><code class="literal">ER_JSON_DOCUMENT_NULL_KEY</code></a>;
      SQLSTATE: <code class="literal">22032</code>
    </p><p>
      Message: JSON documents may not contain NULL member names.
    </p><p>
      <a class="link" href="error-handling.html#error_er_json_document_null_key"><code class="literal">ER_JSON_DOCUMENT_NULL_KEY</code></a> was
      added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_secure_transport_required"></a>
      <a class="indexterm" name="idm46734185596256"></a>

      <a class="indexterm" name="idm46734185595216"></a>

      Error number: <code class="literal">3159</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_secure_transport_required"><code class="literal">ER_SECURE_TRANSPORT_REQUIRED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Connections using insecure transport are prohibited while
      --require_secure_transport=ON.
    </p><p>
      With the <a class="link" href="server-administration.html#sysvar_require_secure_transport"><code class="literal">require_secure_transport</code></a>
      system variable, clients can connect only using secure transports.
      Qualifying connections are those using SSL, a Unix socket file, or
      shared memory.
    </p><p>
      <a class="link" href="error-handling.html#error_er_secure_transport_required"><code class="literal">ER_SECURE_TRANSPORT_REQUIRED</code></a> was
      added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_no_secure_transports_configured"></a>
      <a class="indexterm" name="idm46734185585680"></a>

      <a class="indexterm" name="idm46734185584640"></a>

      Error number: <code class="literal">3160</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_no_secure_transports_configured"><code class="literal">ER_NO_SECURE_TRANSPORTS_CONFIGURED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: No secure transports (SSL or Shared Memory) are
      configured, unable to set --require_secure_transport=ON.
    </p><p>
      The <a class="link" href="server-administration.html#sysvar_require_secure_transport"><code class="literal">require_secure_transport</code></a>
      system variable cannot be enabled if the server does not support
      at least one secure transport. Configure the server with the
      required SSL keys/certificates to enable SSL connections, or
      enable the <a class="link" href="server-administration.html#sysvar_shared_memory"><code class="literal">shared_memory</code></a> system
      variable to enable shared-memory connections.
    </p><p>
      <a class="link" href="error-handling.html#error_er_no_secure_transports_configured"><code class="literal">ER_NO_SECURE_TRANSPORTS_CONFIGURED</code></a>
      was added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_disabled_storage_engine"></a>
      <a class="indexterm" name="idm46734185573744"></a>

      <a class="indexterm" name="idm46734185572704"></a>

      Error number: <code class="literal">3161</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_disabled_storage_engine"><code class="literal">ER_DISABLED_STORAGE_ENGINE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Storage engine %s is disabled (Table creation is
      disallowed).
    </p><p>
      An attempt was made to create a table or tablespace using a
      storage engine listed in the value of the
      <a class="link" href="server-administration.html#sysvar_disabled_storage_engines"><code class="literal">disabled_storage_engines</code></a> system
      variable, or to change an existing table or tablespace to such an
      engine. Choose a different storage engine.
    </p><p>
      <a class="link" href="error-handling.html#error_er_disabled_storage_engine"><code class="literal">ER_DISABLED_STORAGE_ENGINE</code></a> was
      added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_user_does_not_exist"></a>
      <a class="indexterm" name="idm46734185563056"></a>

      <a class="indexterm" name="idm46734185562016"></a>

      Error number: <code class="literal">3162</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_user_does_not_exist"><code class="literal">ER_USER_DOES_NOT_EXIST</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: User %s does not exist.
    </p><p>
      <a class="link" href="error-handling.html#error_er_user_does_not_exist"><code class="literal">ER_USER_DOES_NOT_EXIST</code></a> was added
      in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_user_already_exists"></a>
      <a class="indexterm" name="idm46734185554320"></a>

      <a class="indexterm" name="idm46734185553280"></a>

      Error number: <code class="literal">3163</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_user_already_exists"><code class="literal">ER_USER_ALREADY_EXISTS</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: User %s already exists.
    </p><p>
      <a class="link" href="error-handling.html#error_er_user_already_exists"><code class="literal">ER_USER_ALREADY_EXISTS</code></a> was added
      in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_audit_api_abort"></a>
      <a class="indexterm" name="idm46734185545520"></a>

      <a class="indexterm" name="idm46734185544480"></a>

      Error number: <code class="literal">3164</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_api_abort"><code class="literal">ER_AUDIT_API_ABORT</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Aborted by Audit API ('%s';%d).
    </p><p>
      This error indicates that an audit plugin terminated execution of
      an event. The message typically indicates the event subclass name
      and a numeric status value.
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_api_abort"><code class="literal">ER_AUDIT_API_ABORT</code></a> was added in
      5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_invalid_json_path_array_cell"></a>
      <a class="indexterm" name="idm46734185536272"></a>

      <a class="indexterm" name="idm46734185535168"></a>

      Error number: <code class="literal">3165</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_json_path_array_cell"><code class="literal">ER_INVALID_JSON_PATH_ARRAY_CELL</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: A path expression is not a path to a cell in an array.
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_json_path_array_cell"><code class="literal">ER_INVALID_JSON_PATH_ARRAY_CELL</code></a>
      was added in 5.7.8.
    </p></li><li class="listitem"><p><a name="error_er_bufpool_resize_inprogress"></a>
      <a class="indexterm" name="idm46734185527504"></a>

      <a class="indexterm" name="idm46734185526464"></a>

      Error number: <code class="literal">3166</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_bufpool_resize_inprogress"><code class="literal">ER_BUFPOOL_RESIZE_INPROGRESS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Another buffer pool resize is already in progress.
    </p><p>
      <a class="link" href="error-handling.html#error_er_bufpool_resize_inprogress"><code class="literal">ER_BUFPOOL_RESIZE_INPROGRESS</code></a> was
      added in 5.7.9.
    </p></li><li class="listitem"><p><a name="error_er_feature_disabled_see_doc"></a>
      <a class="indexterm" name="idm46734185518768"></a>

      <a class="indexterm" name="idm46734185517728"></a>

      Error number: <code class="literal">3167</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_feature_disabled_see_doc"><code class="literal">ER_FEATURE_DISABLED_SEE_DOC</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The '%s' feature is disabled; see the documentation for
      '%s'
    </p><p>
      <a class="link" href="error-handling.html#error_er_feature_disabled_see_doc"><code class="literal">ER_FEATURE_DISABLED_SEE_DOC</code></a> was
      added in 5.7.9.
    </p></li><li class="listitem"><p><a name="error_er_server_isnt_available"></a>
      <a class="indexterm" name="idm46734185509952"></a>

      <a class="indexterm" name="idm46734185508912"></a>

      Error number: <code class="literal">3168</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_server_isnt_available"><code class="literal">ER_SERVER_ISNT_AVAILABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Server isn't available
    </p><p>
      <a class="link" href="error-handling.html#error_er_server_isnt_available"><code class="literal">ER_SERVER_ISNT_AVAILABLE</code></a> was added
      in 5.7.9.
    </p></li><li class="listitem"><p><a name="error_er_session_was_killed"></a>
      <a class="indexterm" name="idm46734185501168"></a>

      <a class="indexterm" name="idm46734185500128"></a>

      Error number: <code class="literal">3169</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_session_was_killed"><code class="literal">ER_SESSION_WAS_KILLED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Session was killed
    </p><p>
      <a class="link" href="error-handling.html#error_er_session_was_killed"><code class="literal">ER_SESSION_WAS_KILLED</code></a> was added in
      5.7.9.
    </p></li><li class="listitem"><p><a name="error_er_capacity_exceeded"></a>
      <a class="indexterm" name="idm46734185492448"></a>

      <a class="indexterm" name="idm46734185491408"></a>

      Error number: <code class="literal">3170</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_capacity_exceeded"><code class="literal">ER_CAPACITY_EXCEEDED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Memory capacity of %llu bytes for '%s' exceeded. %s
    </p><p>
      <a class="link" href="error-handling.html#error_er_capacity_exceeded"><code class="literal">ER_CAPACITY_EXCEEDED</code></a> was added in
      5.7.9.
    </p></li><li class="listitem"><p><a name="error_er_capacity_exceeded_in_range_optimizer"></a>
      <a class="indexterm" name="idm46734185483632"></a>

      <a class="indexterm" name="idm46734185482592"></a>

      Error number: <code class="literal">3171</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_capacity_exceeded_in_range_optimizer"><code class="literal">ER_CAPACITY_EXCEEDED_IN_RANGE_OPTIMIZER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Range optimization was not done for this query.
    </p><p>
      <a class="link" href="error-handling.html#error_er_capacity_exceeded_in_range_optimizer"><code class="literal">ER_CAPACITY_EXCEEDED_IN_RANGE_OPTIMIZER</code></a>
      was added in 5.7.9.
    </p></li><li class="listitem"><p><a name="error_er_table_needs_upg_part"></a>
      <a class="indexterm" name="idm46734185474832"></a>

      <a class="indexterm" name="idm46734185473792"></a>

      Error number: <code class="literal">3172</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_needs_upg_part"><code class="literal">ER_TABLE_NEEDS_UPG_PART</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Partitioning upgrade required. Please dump/reload to fix
      it or do: ALTER TABLE `%s`.`%s` UPGRADE PARTITIONING
    </p><p>
      <a class="link" href="error-handling.html#error_er_table_needs_upg_part"><code class="literal">ER_TABLE_NEEDS_UPG_PART</code></a> was added
      in 5.7.9.
    </p></li><li class="listitem"><p><a name="error_er_cant_wait_for_executed_gtid_set_while_owning_a_gtid"></a>
      <a class="indexterm" name="idm46734185465840"></a>

      <a class="indexterm" name="idm46734185464800"></a>

      Error number: <code class="literal">3173</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_wait_for_executed_gtid_set_while_owning_a_gtid"><code class="literal">ER_CANT_WAIT_FOR_EXECUTED_GTID_SET_WHILE_OWNING_A_GTID</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The client holds ownership of the GTID %s. Therefore,
      WAIT_FOR_EXECUTED_GTID_SET cannot wait for this GTID.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cant_wait_for_executed_gtid_set_while_owning_a_gtid"><code class="literal">ER_CANT_WAIT_FOR_EXECUTED_GTID_SET_WHILE_OWNING_A_GTID</code></a>
      was added in 5.7.9.
    </p></li><li class="listitem"><p><a name="error_er_cannot_add_foreign_base_col_virtual"></a>
      <a class="indexterm" name="idm46734185456736"></a>

      <a class="indexterm" name="idm46734185455696"></a>

      Error number: <code class="literal">3174</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cannot_add_foreign_base_col_virtual"><code class="literal">ER_CANNOT_ADD_FOREIGN_BASE_COL_VIRTUAL</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot add foreign key on the base column of indexed
      virtual column.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cannot_add_foreign_base_col_virtual"><code class="literal">ER_CANNOT_ADD_FOREIGN_BASE_COL_VIRTUAL</code></a>
      was added in 5.7.10.
    </p></li><li class="listitem"><p><a name="error_er_cannot_create_virtual_index_constraint"></a>
      <a class="indexterm" name="idm46734185447856"></a>

      <a class="indexterm" name="idm46734185446816"></a>

      Error number: <code class="literal">3175</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cannot_create_virtual_index_constraint"><code class="literal">ER_CANNOT_CREATE_VIRTUAL_INDEX_CONSTRAINT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot create index on virtual column whose base column
      has foreign constraint.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cannot_create_virtual_index_constraint"><code class="literal">ER_CANNOT_CREATE_VIRTUAL_INDEX_CONSTRAINT</code></a>
      was added in 5.7.10.
    </p></li><li class="listitem"><p><a name="error_er_error_on_modifying_gtid_executed_table"></a>
      <a class="indexterm" name="idm46734185438912"></a>

      <a class="indexterm" name="idm46734185437872"></a>

      Error number: <code class="literal">3176</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_error_on_modifying_gtid_executed_table"><code class="literal">ER_ERROR_ON_MODIFYING_GTID_EXECUTED_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Please do not modify the %s table with an XA transaction.
      This is an internal system table used to store GTIDs for committed
      transactions. Although modifying it can lead to an inconsistent
      GTID state, if neccessary you can modify it with a non-XA
      transaction.
    </p><p>
      <a class="link" href="error-handling.html#error_er_error_on_modifying_gtid_executed_table"><code class="literal">ER_ERROR_ON_MODIFYING_GTID_EXECUTED_TABLE</code></a>
      was added in 5.7.11.
    </p></li><li class="listitem"><p><a name="error_er_lock_refused_by_engine"></a>
      <a class="indexterm" name="idm46734185429760"></a>

      <a class="indexterm" name="idm46734185428720"></a>

      Error number: <code class="literal">3177</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_lock_refused_by_engine"><code class="literal">ER_LOCK_REFUSED_BY_ENGINE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Lock acquisition refused by storage engine.
    </p><p>
      <a class="link" href="error-handling.html#error_er_lock_refused_by_engine"><code class="literal">ER_LOCK_REFUSED_BY_ENGINE</code></a> was
      added in 5.7.11.
    </p></li><li class="listitem"><p><a name="error_er_unsupported_alter_online_on_virtual_column"></a>
      <a class="indexterm" name="idm46734185421056"></a>

      <a class="indexterm" name="idm46734185419936"></a>

      Error number: <code class="literal">3178</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unsupported_alter_online_on_virtual_column"><code class="literal">ER_UNSUPPORTED_ALTER_ONLINE_ON_VIRTUAL_COLUMN</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: ADD COLUMN col...VIRTUAL, ADD INDEX(col)
    </p><p>
      <a class="link" href="error-handling.html#error_er_unsupported_alter_online_on_virtual_column"><code class="literal">ER_UNSUPPORTED_ALTER_ONLINE_ON_VIRTUAL_COLUMN</code></a>
      was added in 5.7.11.
    </p></li><li class="listitem"><p><a name="error_er_master_key_rotation_not_supported_by_se"></a>
      <a class="indexterm" name="idm46734185412080"></a>

      <a class="indexterm" name="idm46734185411040"></a>

      Error number: <code class="literal">3179</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_master_key_rotation_not_supported_by_se"><code class="literal">ER_MASTER_KEY_ROTATION_NOT_SUPPORTED_BY_SE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Master key rotation is not supported by storage engine.
    </p><p>
      <a class="link" href="error-handling.html#error_er_master_key_rotation_not_supported_by_se"><code class="literal">ER_MASTER_KEY_ROTATION_NOT_SUPPORTED_BY_SE</code></a>
      was added in 5.7.11.
    </p></li><li class="listitem"><p><a name="error_er_master_key_rotation_error_by_se"></a>
      <a class="indexterm" name="idm46734185403104"></a>

      <a class="indexterm" name="idm46734185402064"></a>

      Error number: <code class="literal">3180</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_master_key_rotation_error_by_se"><code class="literal">ER_MASTER_KEY_ROTATION_ERROR_BY_SE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Encryption key rotation error reported by SE: %s
    </p><p>
      <a class="link" href="error-handling.html#error_er_master_key_rotation_error_by_se"><code class="literal">ER_MASTER_KEY_ROTATION_ERROR_BY_SE</code></a>
      was added in 5.7.11.
    </p></li><li class="listitem"><p><a name="error_er_master_key_rotation_binlog_failed"></a>
      <a class="indexterm" name="idm46734185394256"></a>

      <a class="indexterm" name="idm46734185393216"></a>

      Error number: <code class="literal">3181</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_master_key_rotation_binlog_failed"><code class="literal">ER_MASTER_KEY_ROTATION_BINLOG_FAILED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Write to binlog failed. However, master key rotation has
      been completed successfully.
    </p><p>
      <a class="link" href="error-handling.html#error_er_master_key_rotation_binlog_failed"><code class="literal">ER_MASTER_KEY_ROTATION_BINLOG_FAILED</code></a>
      was added in 5.7.11.
    </p></li><li class="listitem"><p><a name="error_er_master_key_rotation_se_unavailable"></a>
      <a class="indexterm" name="idm46734185385360"></a>

      <a class="indexterm" name="idm46734185384320"></a>

      Error number: <code class="literal">3182</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_master_key_rotation_se_unavailable"><code class="literal">ER_MASTER_KEY_ROTATION_SE_UNAVAILABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Storage engine is not available.
    </p><p>
      <a class="link" href="error-handling.html#error_er_master_key_rotation_se_unavailable"><code class="literal">ER_MASTER_KEY_ROTATION_SE_UNAVAILABLE</code></a>
      was added in 5.7.11.
    </p></li><li class="listitem"><p><a name="error_er_tablespace_cannot_encrypt"></a>
      <a class="indexterm" name="idm46734185376512"></a>

      <a class="indexterm" name="idm46734185375472"></a>

      Error number: <code class="literal">3183</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_tablespace_cannot_encrypt"><code class="literal">ER_TABLESPACE_CANNOT_ENCRYPT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: This tablespace can't be encrypted.
    </p><p>
      <a class="link" href="error-handling.html#error_er_tablespace_cannot_encrypt"><code class="literal">ER_TABLESPACE_CANNOT_ENCRYPT</code></a> was
      added in 5.7.11.
    </p></li><li class="listitem"><p><a name="error_er_invalid_encryption_option"></a>
      <a class="indexterm" name="idm46734185367712"></a>

      <a class="indexterm" name="idm46734185366672"></a>

      Error number: <code class="literal">3184</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_invalid_encryption_option"><code class="literal">ER_INVALID_ENCRYPTION_OPTION</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Invalid encryption option.
    </p><p>
      <a class="link" href="error-handling.html#error_er_invalid_encryption_option"><code class="literal">ER_INVALID_ENCRYPTION_OPTION</code></a> was
      added in 5.7.11.
    </p></li><li class="listitem"><p><a name="error_er_cannot_find_key_in_keyring"></a>
      <a class="indexterm" name="idm46734185358992"></a>

      <a class="indexterm" name="idm46734185357888"></a>

      Error number: <code class="literal">3185</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cannot_find_key_in_keyring"><code class="literal">ER_CANNOT_FIND_KEY_IN_KEYRING</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Can't find master key from keyring, please check in the
      server log if a keyring plugin is loaded and initialized
      successfully.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cannot_find_key_in_keyring"><code class="literal">ER_CANNOT_FIND_KEY_IN_KEYRING</code></a> was
      added in 5.7.11.
    </p></li><li class="listitem"><p><a name="error_er_capacity_exceeded_in_parser"></a>
      <a class="indexterm" name="idm46734185350144"></a>

      <a class="indexterm" name="idm46734185349040"></a>

      Error number: <code class="literal">3186</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_capacity_exceeded_in_parser"><code class="literal">ER_CAPACITY_EXCEEDED_IN_PARSER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Parser bailed out for this query.
    </p><p>
      <a class="link" href="error-handling.html#error_er_capacity_exceeded_in_parser"><code class="literal">ER_CAPACITY_EXCEEDED_IN_PARSER</code></a> was
      added in 5.7.12.
    </p></li><li class="listitem"><p><a name="error_er_unsupported_alter_encryption_inplace"></a>
      <a class="indexterm" name="idm46734185341296"></a>

      <a class="indexterm" name="idm46734185340256"></a>

      Error number: <code class="literal">3187</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_unsupported_alter_encryption_inplace"><code class="literal">ER_UNSUPPORTED_ALTER_ENCRYPTION_INPLACE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot alter encryption attribute by inplace algorithm.
    </p><p>
      <a class="link" href="error-handling.html#error_er_unsupported_alter_encryption_inplace"><code class="literal">ER_UNSUPPORTED_ALTER_ENCRYPTION_INPLACE</code></a>
      was added in 5.7.13.
    </p></li><li class="listitem"><p><a name="error_er_keyring_udf_keyring_service_error"></a>
      <a class="indexterm" name="idm46734185332368"></a>

      <a class="indexterm" name="idm46734185331328"></a>

      Error number: <code class="literal">3188</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_keyring_udf_keyring_service_error"><code class="literal">ER_KEYRING_UDF_KEYRING_SERVICE_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Function '%s' failed because underlying keyring service
      returned an error. Please check if a keyring plugin is installed
      and that provided arguments are valid for the keyring you are
      using.
    </p><p>
      <a class="link" href="error-handling.html#error_er_keyring_udf_keyring_service_error"><code class="literal">ER_KEYRING_UDF_KEYRING_SERVICE_ERROR</code></a>
      was added in 5.7.13.
    </p></li><li class="listitem"><p><a name="error_er_user_column_old_length"></a>
      <a class="indexterm" name="idm46734185323456"></a>

      <a class="indexterm" name="idm46734185322416"></a>

      Error number: <code class="literal">3189</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_user_column_old_length"><code class="literal">ER_USER_COLUMN_OLD_LENGTH</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: It seems that your db schema is old. The %s column is 77
      characters long and should be 93 characters long. Please run
      mysql_upgrade.
    </p><p>
      <a class="link" href="error-handling.html#error_er_user_column_old_length"><code class="literal">ER_USER_COLUMN_OLD_LENGTH</code></a> was
      added in 5.7.13.
    </p></li><li class="listitem"><p><a name="error_er_cant_reset_master"></a>
      <a class="indexterm" name="idm46734185314608"></a>

      <a class="indexterm" name="idm46734185313568"></a>

      Error number: <code class="literal">3190</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_reset_master"><code class="literal">ER_CANT_RESET_MASTER</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: RESET MASTER is not allowed because %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cant_reset_master"><code class="literal">ER_CANT_RESET_MASTER</code></a> was added in
      5.7.14.
    </p></li><li class="listitem"><p><a name="error_er_group_replication_max_group_size"></a>
      <a class="indexterm" name="idm46734185305872"></a>

      <a class="indexterm" name="idm46734185304832"></a>

      Error number: <code class="literal">3191</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_group_replication_max_group_size"><code class="literal">ER_GROUP_REPLICATION_MAX_GROUP_SIZE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The START GROUP_REPLICATION command failed since the
      group already has 9 members.
    </p><p>
      <a class="link" href="error-handling.html#error_er_group_replication_max_group_size"><code class="literal">ER_GROUP_REPLICATION_MAX_GROUP_SIZE</code></a>
      was added in 5.7.14.
    </p></li><li class="listitem"><p><a name="error_er_cannot_add_foreign_base_col_stored"></a>
      <a class="indexterm" name="idm46734185296976"></a>

      <a class="indexterm" name="idm46734185295936"></a>

      Error number: <code class="literal">3192</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cannot_add_foreign_base_col_stored"><code class="literal">ER_CANNOT_ADD_FOREIGN_BASE_COL_STORED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Cannot add foreign key on the base column of stored
      column.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cannot_add_foreign_base_col_stored"><code class="literal">ER_CANNOT_ADD_FOREIGN_BASE_COL_STORED</code></a>
      was added in 5.7.14.
    </p></li><li class="listitem"><p><a name="error_er_table_referenced"></a>
      <a class="indexterm" name="idm46734185288160"></a>

      <a class="indexterm" name="idm46734185287120"></a>

      Error number: <code class="literal">3193</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_table_referenced"><code class="literal">ER_TABLE_REFERENCED</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Cannot complete the operation because table is referenced
      by another connection.
    </p><p>
      <a class="link" href="error-handling.html#error_er_table_referenced"><code class="literal">ER_TABLE_REFERENCED</code></a> was added in
      5.7.14.
    </p></li><li class="listitem"><p><a name="error_er_partition_engine_deprecated_for_table"></a>
      <a class="indexterm" name="idm46734185279312"></a>

      <a class="indexterm" name="idm46734185278272"></a>

      Error number: <code class="literal">3194</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_partition_engine_deprecated_for_table"><code class="literal">ER_PARTITION_ENGINE_DEPRECATED_FOR_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The partition engine, used by table '%s.%s', is
      deprecated and will be removed in a future release. Please use
      native partitioning instead.
    </p><p>
      <a class="link" href="error-handling.html#error_er_partition_engine_deprecated_for_table"><code class="literal">ER_PARTITION_ENGINE_DEPRECATED_FOR_TABLE</code></a>
      was added in 5.7.17.
    </p></li><li class="listitem"><p><a name="error_er_warn_using_geomfromwkb_to_set_srid_zero"></a>
      <a class="indexterm" name="idm46734185270240"></a>

      <a class="indexterm" name="idm46734185269200"></a>

      Error number: <code class="literal">3195</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_using_geomfromwkb_to_set_srid_zero"><code class="literal">ER_WARN_USING_GEOMFROMWKB_TO_SET_SRID_ZERO</code></a>;
      SQLSTATE: <code class="literal">01000</code>
    </p><p>
      Message: %s(geometry) is deprecated and will be replaced by
      st_srid(geometry, 0) in a future version. Use
      %s(st_aswkb(geometry), 0) instead.
    </p><p>
      <a class="link" href="error-handling.html#error_er_warn_using_geomfromwkb_to_set_srid_zero"><code class="literal">ER_WARN_USING_GEOMFROMWKB_TO_SET_SRID_ZERO</code></a>
      was added in 5.7.19.
    </p></li><li class="listitem"><p><a name="error_er_warn_using_geomfromwkb_to_set_srid"></a>
      <a class="indexterm" name="idm46734185261184"></a>

      <a class="indexterm" name="idm46734185260144"></a>

      Error number: <code class="literal">3196</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_warn_using_geomfromwkb_to_set_srid"><code class="literal">ER_WARN_USING_GEOMFROMWKB_TO_SET_SRID</code></a>;
      SQLSTATE: <code class="literal">01000</code>
    </p><p>
      Message: %s(geometry, srid) is deprecated and will be replaced by
      st_srid(geometry, srid) in a future version. Use
      %s(st_aswkb(geometry), srid) instead.
    </p><p>
      <a class="link" href="error-handling.html#error_er_warn_using_geomfromwkb_to_set_srid"><code class="literal">ER_WARN_USING_GEOMFROMWKB_TO_SET_SRID</code></a>
      was added in 5.7.19.
    </p></li><li class="listitem"><p><a name="error_er_xa_retry"></a>
      <a class="indexterm" name="idm46734185252320"></a>

      <a class="indexterm" name="idm46734185251280"></a>

      Error number: <code class="literal">3197</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_xa_retry"><code class="literal">ER_XA_RETRY</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: The resource manager is not able to commit the
      transaction branch at this time. Please retry later.
    </p><p>
      <a class="link" href="error-handling.html#error_er_xa_retry"><code class="literal">ER_XA_RETRY</code></a> was added in 5.7.19.
    </p></li><li class="listitem"><p><a name="error_er_keyring_aws_udf_aws_kms_error"></a>
      <a class="indexterm" name="idm46734185243632"></a>

      <a class="indexterm" name="idm46734185242528"></a>

      Error number: <code class="literal">3198</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_keyring_aws_udf_aws_kms_error"><code class="literal">ER_KEYRING_AWS_UDF_AWS_KMS_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Function %s failed due to: %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_keyring_aws_udf_aws_kms_error"><code class="literal">ER_KEYRING_AWS_UDF_AWS_KMS_ERROR</code></a>
      was added in 5.7.19.
    </p></li><li class="listitem"><p><a name="error_er_binlog_unsafe_xa"></a>
      <a class="indexterm" name="idm46734185234768"></a>

      <a class="indexterm" name="idm46734185233728"></a>

      Error number: <code class="literal">3199</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_xa"><code class="literal">ER_BINLOG_UNSAFE_XA</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Statement is unsafe because it is being used inside a XA
      transaction. Concurrent XA transactions may deadlock on slaves
      when replicated using statements.
    </p><p>
      <a class="link" href="error-handling.html#error_er_binlog_unsafe_xa"><code class="literal">ER_BINLOG_UNSAFE_XA</code></a> was added in
      5.7.20.
    </p></li><li class="listitem"><p><a name="error_er_udf_error"></a>
      <a class="indexterm" name="idm46734185225872"></a>

      <a class="indexterm" name="idm46734185224832"></a>

      Error number: <code class="literal">3200</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_udf_error"><code class="literal">ER_UDF_ERROR</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: %s UDF failed; %s
    </p><p>
      <a class="link" href="error-handling.html#error_er_udf_error"><code class="literal">ER_UDF_ERROR</code></a> was added in 5.7.21.
    </p></li><li class="listitem"><p><a name="error_er_keyring_migration_failure"></a>
      <a class="indexterm" name="idm46734185217280"></a>

      <a class="indexterm" name="idm46734185216240"></a>

      Error number: <code class="literal">3201</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_keyring_migration_failure"><code class="literal">ER_KEYRING_MIGRATION_FAILURE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Can not perform keyring migration : %s
    </p><p>
      <a class="link" href="error-handling.html#error_er_keyring_migration_failure"><code class="literal">ER_KEYRING_MIGRATION_FAILURE</code></a> was
      added in 5.7.21.
    </p></li><li class="listitem"><p><a name="error_er_keyring_access_denied_error"></a>
      <a class="indexterm" name="idm46734185208480"></a>

      <a class="indexterm" name="idm46734185207376"></a>

      Error number: <code class="literal">3202</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_keyring_access_denied_error"><code class="literal">ER_KEYRING_ACCESS_DENIED_ERROR</code></a>;
      SQLSTATE: <code class="literal">42000</code>
    </p><p>
      Message: Access denied; you need %s privileges for this operation
    </p><p>
      <a class="link" href="error-handling.html#error_er_keyring_access_denied_error"><code class="literal">ER_KEYRING_ACCESS_DENIED_ERROR</code></a> was
      added in 5.7.21.
    </p></li><li class="listitem"><p><a name="error_er_keyring_migration_status"></a>
      <a class="indexterm" name="idm46734185199648"></a>

      <a class="indexterm" name="idm46734185198608"></a>

      Error number: <code class="literal">3203</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_keyring_migration_status"><code class="literal">ER_KEYRING_MIGRATION_STATUS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Keyring migration %s.
    </p><p>
      <a class="link" href="error-handling.html#error_er_keyring_migration_status"><code class="literal">ER_KEYRING_MIGRATION_STATUS</code></a> was
      added in 5.7.21.
    </p></li><li class="listitem"><p><a name="error_er_plugin_failed_to_open_tables"></a>
      <a class="indexterm" name="idm46734185190928"></a>

      <a class="indexterm" name="idm46734185189824"></a>

      Error number: <code class="literal">3204</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_plugin_failed_to_open_tables"><code class="literal">ER_PLUGIN_FAILED_TO_OPEN_TABLES</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Failed to open the %s filter tables.
    </p><p>
      <a class="link" href="error-handling.html#error_er_plugin_failed_to_open_tables"><code class="literal">ER_PLUGIN_FAILED_TO_OPEN_TABLES</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_plugin_failed_to_open_table"></a>
      <a class="indexterm" name="idm46734185182176"></a>

      <a class="indexterm" name="idm46734185181072"></a>

      Error number: <code class="literal">3205</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_plugin_failed_to_open_table"><code class="literal">ER_PLUGIN_FAILED_TO_OPEN_TABLE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Failed to open '%s.%s' %s table.
    </p><p>
      <a class="link" href="error-handling.html#error_er_plugin_failed_to_open_table"><code class="literal">ER_PLUGIN_FAILED_TO_OPEN_TABLE</code></a> was
      added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_no_keyring_plugin_installed"></a>
      <a class="indexterm" name="idm46734185173392"></a>

      <a class="indexterm" name="idm46734185172352"></a>

      Error number: <code class="literal">3206</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_no_keyring_plugin_installed"><code class="literal">ER_AUDIT_LOG_NO_KEYRING_PLUGIN_INSTALLED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: No keyring plugin installed.
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_no_keyring_plugin_installed"><code class="literal">ER_AUDIT_LOG_NO_KEYRING_PLUGIN_INSTALLED</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_encryption_password_has_not_been_set"></a>
      <a class="indexterm" name="idm46734185164512"></a>

      <a class="indexterm" name="idm46734185163392"></a>

      Error number: <code class="literal">3207</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_encryption_password_has_not_been_set"><code class="literal">ER_AUDIT_LOG_ENCRYPTION_PASSWORD_HAS_NOT_BEEN_SET</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Audit log encryption password has not been set; it will
      be generated automatically. Use audit_log_encryption_password_get
      to obtain the password or audit_log_encryption_password_set to set
      a new one.
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_encryption_password_has_not_been_set"><code class="literal">ER_AUDIT_LOG_ENCRYPTION_PASSWORD_HAS_NOT_BEEN_SET</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_could_not_create_aes_key"></a>
      <a class="indexterm" name="idm46734185155408"></a>

      <a class="indexterm" name="idm46734185154368"></a>

      Error number: <code class="literal">3208</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_could_not_create_aes_key"><code class="literal">ER_AUDIT_LOG_COULD_NOT_CREATE_AES_KEY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Could not create AES key. OpenSSL's EVP_BytesToKey
      function failed.
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_could_not_create_aes_key"><code class="literal">ER_AUDIT_LOG_COULD_NOT_CREATE_AES_KEY</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_encryption_password_cannot_be_fetched"></a>
      <a class="indexterm" name="idm46734185146416"></a>

      <a class="indexterm" name="idm46734185145376"></a>

      Error number: <code class="literal">3209</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_encryption_password_cannot_be_fetched"><code class="literal">ER_AUDIT_LOG_ENCRYPTION_PASSWORD_CANNOT_BE_FETCHED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Audit log encryption password cannot be fetched from the
      keyring. Password used so far is used for encryption.
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_encryption_password_cannot_be_fetched"><code class="literal">ER_AUDIT_LOG_ENCRYPTION_PASSWORD_CANNOT_BE_FETCHED</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_json_filtering_not_enabled"></a>
      <a class="indexterm" name="idm46734185137296"></a>

      <a class="indexterm" name="idm46734185136256"></a>

      Error number: <code class="literal">3210</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_json_filtering_not_enabled"><code class="literal">ER_AUDIT_LOG_JSON_FILTERING_NOT_ENABLED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Audit Log filtering has not been installed.
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_json_filtering_not_enabled"><code class="literal">ER_AUDIT_LOG_JSON_FILTERING_NOT_ENABLED</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_udf_insufficient_privilege"></a>
      <a class="indexterm" name="idm46734185128528"></a>

      <a class="indexterm" name="idm46734185127488"></a>

      Error number: <code class="literal">3211</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_udf_insufficient_privilege"><code class="literal">ER_AUDIT_LOG_UDF_INSUFFICIENT_PRIVILEGE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Request ignored for '%s'@'%s'. SUPER_ACL needed to
      perform operation
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_udf_insufficient_privilege"><code class="literal">ER_AUDIT_LOG_UDF_INSUFFICIENT_PRIVILEGE</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_super_privilege_required"></a>
      <a class="indexterm" name="idm46734185119584"></a>

      <a class="indexterm" name="idm46734185118544"></a>

      Error number: <code class="literal">3212</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_super_privilege_required"><code class="literal">ER_AUDIT_LOG_SUPER_PRIVILEGE_REQUIRED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: SUPER privilege required for '%s'@'%s' user.
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_super_privilege_required"><code class="literal">ER_AUDIT_LOG_SUPER_PRIVILEGE_REQUIRED</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_could_not_reinitialize_audit_log_filters"></a>
      <a class="indexterm" name="idm46734185110672"></a>

      <a class="indexterm" name="idm46734185109632"></a>

      Error number: <code class="literal">3213</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_could_not_reinitialize_audit_log_filters"><code class="literal">ER_COULD_NOT_REINITIALIZE_AUDIT_LOG_FILTERS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Could not reinitialize audit log filters.
    </p><p>
      <a class="link" href="error-handling.html#error_er_could_not_reinitialize_audit_log_filters"><code class="literal">ER_COULD_NOT_REINITIALIZE_AUDIT_LOG_FILTERS</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_udf_invalid_argument_type"></a>
      <a class="indexterm" name="idm46734185101776"></a>

      <a class="indexterm" name="idm46734185100736"></a>

      Error number: <code class="literal">3214</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_udf_invalid_argument_type"><code class="literal">ER_AUDIT_LOG_UDF_INVALID_ARGUMENT_TYPE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Invalid argument type
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_udf_invalid_argument_type"><code class="literal">ER_AUDIT_LOG_UDF_INVALID_ARGUMENT_TYPE</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_udf_invalid_argument_count"></a>
      <a class="indexterm" name="idm46734185092944"></a>

      <a class="indexterm" name="idm46734185091904"></a>

      Error number: <code class="literal">3215</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_udf_invalid_argument_count"><code class="literal">ER_AUDIT_LOG_UDF_INVALID_ARGUMENT_COUNT</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Invalid argument count
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_udf_invalid_argument_count"><code class="literal">ER_AUDIT_LOG_UDF_INVALID_ARGUMENT_COUNT</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_has_not_been_installed"></a>
      <a class="indexterm" name="idm46734185084048"></a>

      <a class="indexterm" name="idm46734185083008"></a>

      Error number: <code class="literal">3216</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_has_not_been_installed"><code class="literal">ER_AUDIT_LOG_HAS_NOT_BEEN_INSTALLED</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: audit_log plugin has not been installed using INSTALL
      PLUGIN syntax.
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_has_not_been_installed"><code class="literal">ER_AUDIT_LOG_HAS_NOT_BEEN_INSTALLED</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_udf_read_invalid_max_array_length_arg_type"></a>
      <a class="indexterm" name="idm46734185075120"></a>

      <a class="indexterm" name="idm46734185074080"></a>

      Error number: <code class="literal">3217</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_udf_read_invalid_max_array_length_arg_type"><code class="literal">ER_AUDIT_LOG_UDF_READ_INVALID_MAX_ARRAY_LENGTH_ARG_TYPE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Invalid "max_array_length" argument type.
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_udf_read_invalid_max_array_length_arg_type"><code class="literal">ER_AUDIT_LOG_UDF_READ_INVALID_MAX_ARRAY_LENGTH_ARG_TYPE</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_udf_read_invalid_max_array_length_arg_value"></a>
      <a class="indexterm" name="idm46734185065984"></a>

      <a class="indexterm" name="idm46734185064944"></a>

      Error number: <code class="literal">3218</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_udf_read_invalid_max_array_length_arg_value"><code class="literal">ER_AUDIT_LOG_UDF_READ_INVALID_MAX_ARRAY_LENGTH_ARG_VALUE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Invalid "max_array_length" argument value.
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_udf_read_invalid_max_array_length_arg_value"><code class="literal">ER_AUDIT_LOG_UDF_READ_INVALID_MAX_ARRAY_LENGTH_ARG_VALUE</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_json_filter_parsing_error"></a>
      <a class="indexterm" name="idm46734185056896"></a>

      <a class="indexterm" name="idm46734185055856"></a>

      Error number: <code class="literal">3219</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_json_filter_parsing_error"><code class="literal">ER_AUDIT_LOG_JSON_FILTER_PARSING_ERROR</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: %s
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_json_filter_parsing_error"><code class="literal">ER_AUDIT_LOG_JSON_FILTER_PARSING_ERROR</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_json_filter_name_cannot_be_empty"></a>
      <a class="indexterm" name="idm46734185048096"></a>

      <a class="indexterm" name="idm46734185046976"></a>

      Error number: <code class="literal">3220</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_json_filter_name_cannot_be_empty"><code class="literal">ER_AUDIT_LOG_JSON_FILTER_NAME_CANNOT_BE_EMPTY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Filter name cannot be empty.
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_json_filter_name_cannot_be_empty"><code class="literal">ER_AUDIT_LOG_JSON_FILTER_NAME_CANNOT_BE_EMPTY</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_json_user_name_cannot_be_empty"></a>
      <a class="indexterm" name="idm46734185039072"></a>

      <a class="indexterm" name="idm46734185038032"></a>

      Error number: <code class="literal">3221</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_json_user_name_cannot_be_empty"><code class="literal">ER_AUDIT_LOG_JSON_USER_NAME_CANNOT_BE_EMPTY</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: User cannot be empty.
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_json_user_name_cannot_be_empty"><code class="literal">ER_AUDIT_LOG_JSON_USER_NAME_CANNOT_BE_EMPTY</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_json_filter_does_not_exists"></a>
      <a class="indexterm" name="idm46734185030064"></a>

      <a class="indexterm" name="idm46734185029024"></a>

      Error number: <code class="literal">3222</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_json_filter_does_not_exists"><code class="literal">ER_AUDIT_LOG_JSON_FILTER_DOES_NOT_EXISTS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Specified filter has not been found.
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_json_filter_does_not_exists"><code class="literal">ER_AUDIT_LOG_JSON_FILTER_DOES_NOT_EXISTS</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_user_first_character_must_be_alphanumeric"></a>
      <a class="indexterm" name="idm46734185021120"></a>

      <a class="indexterm" name="idm46734185020080"></a>

      Error number: <code class="literal">3223</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_user_first_character_must_be_alphanumeric"><code class="literal">ER_AUDIT_LOG_USER_FIRST_CHARACTER_MUST_BE_ALPHANUMERIC</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: First character of the user name must be alphanumeric.
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_user_first_character_must_be_alphanumeric"><code class="literal">ER_AUDIT_LOG_USER_FIRST_CHARACTER_MUST_BE_ALPHANUMERIC</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_user_name_invalid_character"></a>
      <a class="indexterm" name="idm46734185012064"></a>

      <a class="indexterm" name="idm46734185011024"></a>

      Error number: <code class="literal">3224</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_user_name_invalid_character"><code class="literal">ER_AUDIT_LOG_USER_NAME_INVALID_CHARACTER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Invalid character in the user name.
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_user_name_invalid_character"><code class="literal">ER_AUDIT_LOG_USER_NAME_INVALID_CHARACTER</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_audit_log_host_name_invalid_character"></a>
      <a class="indexterm" name="idm46734185003184"></a>

      <a class="indexterm" name="idm46734185002144"></a>

      Error number: <code class="literal">3225</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_audit_log_host_name_invalid_character"><code class="literal">ER_AUDIT_LOG_HOST_NAME_INVALID_CHARACTER</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Invalid character in the host name.
    </p><p>
      <a class="link" href="error-handling.html#error_er_audit_log_host_name_invalid_character"><code class="literal">ER_AUDIT_LOG_HOST_NAME_INVALID_CHARACTER</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_warn_deprecated_maxdb_sql_mode_for_timestamp"></a>
      <a class="indexterm" name="idm46734184994224"></a>

      <a class="indexterm" name="idm46734184993184"></a>

      Error number: <code class="literal">3226</code>; Symbol:
      <a class="link" href="error-handling.html#error_warn_deprecated_maxdb_sql_mode_for_timestamp"><code class="literal">WARN_DEPRECATED_MAXDB_SQL_MODE_FOR_TIMESTAMP</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: With the MAXDB SQL mode enabled, TIMESTAMP is identical
      with DATETIME. The MAXDB SQL mode is deprecated and will be
      removed in a future release. Please disable the MAXDB SQL mode and
      use DATETIME instead.
    </p><p>
      <a class="link" href="error-handling.html#error_warn_deprecated_maxdb_sql_mode_for_timestamp"><code class="literal">WARN_DEPRECATED_MAXDB_SQL_MODE_FOR_TIMESTAMP</code></a>
      was added in 5.7.22.
    </p></li><li class="listitem"><p><a name="error_er_xa_replication_filters"></a>
      <a class="indexterm" name="idm46734184985120"></a>

      <a class="indexterm" name="idm46734184984080"></a>

      Error number: <code class="literal">3227</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_xa_replication_filters"><code class="literal">ER_XA_REPLICATION_FILTERS</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: The use of replication filters with XA transactions is
      not supported, and can lead to an undefined state in the
      replication slave.
    </p><p>
      <a class="link" href="error-handling.html#error_er_xa_replication_filters"><code class="literal">ER_XA_REPLICATION_FILTERS</code></a> was
      added in 5.7.23.
    </p></li><li class="listitem"><p><a name="error_er_cant_open_error_log"></a>
      <a class="indexterm" name="idm46734184976352"></a>

      <a class="indexterm" name="idm46734184975312"></a>

      Error number: <code class="literal">3228</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_open_error_log"><code class="literal">ER_CANT_OPEN_ERROR_LOG</code></a>; SQLSTATE:
      <code class="literal">HY000</code>
    </p><p>
      Message: Could not open file '%s' for error logging%s%s
    </p><p>
      <a class="link" href="error-handling.html#error_er_cant_open_error_log"><code class="literal">ER_CANT_OPEN_ERROR_LOG</code></a> was added
      in 5.7.24.
    </p></li><li class="listitem"><p><a name="error_er_grouping_on_timestamp_in_dst"></a>
      <a class="indexterm" name="idm46734184967600"></a>

      <a class="indexterm" name="idm46734184966496"></a>

      Error number: <code class="literal">3229</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_grouping_on_timestamp_in_dst"><code class="literal">ER_GROUPING_ON_TIMESTAMP_IN_DST</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Grouping on temporal is non-deterministic for timezones
      having DST. Please consider switching to UTC for this query.
    </p><p>
      <a class="link" href="error-handling.html#error_er_grouping_on_timestamp_in_dst"><code class="literal">ER_GROUPING_ON_TIMESTAMP_IN_DST</code></a>
      was added in 5.7.27.
    </p></li><li class="listitem"><p><a name="error_er_cant_start_server_named_pipe"></a>
      <a class="indexterm" name="idm46734184958768"></a>

      <a class="indexterm" name="idm46734184957664"></a>

      Error number: <code class="literal">3230</code>; Symbol:
      <a class="link" href="error-handling.html#error_er_cant_start_server_named_pipe"><code class="literal">ER_CANT_START_SERVER_NAMED_PIPE</code></a>;
      SQLSTATE: <code class="literal">HY000</code>
    </p><p>
      Message: Can't start server : Named Pipe "%s" already in use.
    </p><p>
      <a class="link" href="error-handling.html#error_er_cant_start_server_named_pipe"><code class="literal">ER_CANT_START_SERVER_NAMED_PIPE</code></a>
      was added in 5.7.27.
</p></li></ul>
</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="client-error-reference"></a>B.3.2 Client Error Message Reference</h3>

</div>

</div>

</div>
<p>
        Client error messages originate from within the MySQL client
        library. Here is an example client error message, as displayed
        by the <a class="link" href="programs.html#mysql" title="4.5.1 mysql — The MySQL Command-Line Client"><span class="command"><strong>mysql</strong></span></a> client:
      </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>mysql -h no-such-host</code></strong>
ERROR 2005 (HY000): Unknown MySQL server host 'no-such-host' (0)
</pre><p>
        Each client error message includes an error code, SQLSTATE
        value, and message string, as described in
        <a class="xref" href="error-handling.html#error-message-components" title="B.1 Error Message Sources and Components">Section B.1, “Error Message Sources and Components”</a>. These components are
        available as described in <a class="xref" href="error-handling.html#error-interfaces" title="B.2 Error Information Interfaces">Section B.2, “Error Information Interfaces”</a>.
        For client errors, the SQLSTATE value is always
        <code class="literal">'HY000'</code> (general error), so it is not
        meaningful for distinguishing one client error from another.
      </p><p>
        The client library also makes available to host client programs
        any errors that originate on the server side and are recieved by
        the client from the server. For a list of server-side errors,
        see <a class="xref" href="error-handling.html#server-error-reference" title="B.3.1 Server Error Message Reference">Section B.3.1, “Server Error Message Reference”</a>.
      </p><p>
        In addition to the errors in the following list, the client
        library can also produce error messages that have error codes in
        the range from 1 to 999. See
        <a class="xref" href="error-handling.html#global-error-reference" title="B.3.3 Global Error Message Reference">Section B.3.3, “Global Error Message Reference”</a>
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><a name="error_cr_unknown_error"></a>
      <a class="indexterm" name="idm46734184938880"></a>

      <a class="indexterm" name="idm46734184937824"></a>

      Error number: <code class="literal">2000</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_unknown_error"><code class="literal">CR_UNKNOWN_ERROR</code></a>;
    </p><p>
      Message: Unknown MySQL error
    </p></li><li class="listitem"><p><a name="error_cr_socket_create_error"></a>
      <a class="indexterm" name="idm46734184932688"></a>

      <a class="indexterm" name="idm46734184931648"></a>

      Error number: <code class="literal">2001</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_socket_create_error"><code class="literal">CR_SOCKET_CREATE_ERROR</code></a>;
    </p><p>
      Message: Can't create UNIX socket (%d)
    </p></li><li class="listitem"><p><a name="error_cr_connection_error"></a>
      <a class="indexterm" name="idm46734184926416"></a>

      <a class="indexterm" name="idm46734184925376"></a>

      Error number: <code class="literal">2002</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_connection_error"><code class="literal">CR_CONNECTION_ERROR</code></a>;
    </p><p>
      Message: Can't connect to local MySQL server through socket '%s'
      (%d)
    </p></li><li class="listitem"><p><a name="error_cr_conn_host_error"></a>
      <a class="indexterm" name="idm46734184920112"></a>

      <a class="indexterm" name="idm46734184919072"></a>

      Error number: <code class="literal">2003</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_conn_host_error"><code class="literal">CR_CONN_HOST_ERROR</code></a>;
    </p><p>
      Message: Can't connect to MySQL server on '%s' (%d)
    </p></li><li class="listitem"><p><a name="error_cr_ipsock_error"></a>
      <a class="indexterm" name="idm46734184913888"></a>

      <a class="indexterm" name="idm46734184912880"></a>

      Error number: <code class="literal">2004</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_ipsock_error"><code class="literal">CR_IPSOCK_ERROR</code></a>;
    </p><p>
      Message: Can't create TCP/IP socket (%d)
    </p></li><li class="listitem"><p><a name="error_cr_unknown_host"></a>
      <a class="indexterm" name="idm46734184907728"></a>

      <a class="indexterm" name="idm46734184906672"></a>

      Error number: <code class="literal">2005</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_unknown_host"><code class="literal">CR_UNKNOWN_HOST</code></a>;
    </p><p>
      Message: Unknown MySQL server host '%s' (%d)
    </p></li><li class="listitem"><p><a name="error_cr_server_gone_error"></a>
      <a class="indexterm" name="idm46734184901456"></a>

      <a class="indexterm" name="idm46734184900416"></a>

      Error number: <code class="literal">2006</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_server_gone_error"><code class="literal">CR_SERVER_GONE_ERROR</code></a>;
    </p><p>
      Message: MySQL server has gone away
    </p></li><li class="listitem"><p><a name="error_cr_version_error"></a>
      <a class="indexterm" name="idm46734184895184"></a>

      <a class="indexterm" name="idm46734184894176"></a>

      Error number: <code class="literal">2007</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_version_error"><code class="literal">CR_VERSION_ERROR</code></a>;
    </p><p>
      Message: Protocol mismatch; server version = %d, client version =
      %d
    </p></li><li class="listitem"><p><a name="error_cr_out_of_memory"></a>
      <a class="indexterm" name="idm46734184889056"></a>

      <a class="indexterm" name="idm46734184888000"></a>

      Error number: <code class="literal">2008</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_out_of_memory"><code class="literal">CR_OUT_OF_MEMORY</code></a>;
    </p><p>
      Message: MySQL client ran out of memory
    </p></li><li class="listitem"><p><a name="error_cr_wrong_host_info"></a>
      <a class="indexterm" name="idm46734184882752"></a>

      <a class="indexterm" name="idm46734184881712"></a>

      Error number: <code class="literal">2009</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_wrong_host_info"><code class="literal">CR_WRONG_HOST_INFO</code></a>;
    </p><p>
      Message: Wrong host info
    </p></li><li class="listitem"><p><a name="error_cr_localhost_connection"></a>
      <a class="indexterm" name="idm46734184876448"></a>

      <a class="indexterm" name="idm46734184875408"></a>

      Error number: <code class="literal">2010</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_localhost_connection"><code class="literal">CR_LOCALHOST_CONNECTION</code></a>;
    </p><p>
      Message: Localhost via UNIX socket
    </p></li><li class="listitem"><p><a name="error_cr_tcp_connection"></a>
      <a class="indexterm" name="idm46734184870176"></a>

      <a class="indexterm" name="idm46734184869120"></a>

      Error number: <code class="literal">2011</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_tcp_connection"><code class="literal">CR_TCP_CONNECTION</code></a>;
    </p><p>
      Message: %s via TCP/IP
    </p></li><li class="listitem"><p><a name="error_cr_server_handshake_err"></a>
      <a class="indexterm" name="idm46734184863824"></a>

      <a class="indexterm" name="idm46734184862784"></a>

      Error number: <code class="literal">2012</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_server_handshake_err"><code class="literal">CR_SERVER_HANDSHAKE_ERR</code></a>;
    </p><p>
      Message: Error in server handshake
    </p></li><li class="listitem"><p><a name="error_cr_server_lost"></a>
      <a class="indexterm" name="idm46734184857488"></a>

      <a class="indexterm" name="idm46734184856480"></a>

      Error number: <code class="literal">2013</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_server_lost"><code class="literal">CR_SERVER_LOST</code></a>;
    </p><p>
      Message: Lost connection to MySQL server during query
    </p></li><li class="listitem"><p><a name="error_cr_commands_out_of_sync"></a>
      <a class="indexterm" name="idm46734184851264"></a>

      <a class="indexterm" name="idm46734184850224"></a>

      Error number: <code class="literal">2014</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_commands_out_of_sync"><code class="literal">CR_COMMANDS_OUT_OF_SYNC</code></a>;
    </p><p>
      Message: Commands out of sync; you can't run this command now
    </p><p>
      Commands were executed in an improper order. This error occurs
      when a function is called that is not appropriate for the current
      state of the connection. For example, if
      <a class="link" href="connectors-apis.html#mysql-stmt-fetch" title="27.7.10.11 mysql_stmt_fetch()"><code class="literal">mysql_stmt_fetch()</code></a> is not called
      enough times to read an entire result set (that is, enough times
      to return <code class="literal">MYSQL_NO_DATA</code>), this error may occur
      for the following C API call.
    </p></li><li class="listitem"><p><a name="error_cr_namedpipe_connection"></a>
      <a class="indexterm" name="idm46734184842304"></a>

      <a class="indexterm" name="idm46734184841264"></a>

      Error number: <code class="literal">2015</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_namedpipe_connection"><code class="literal">CR_NAMEDPIPE_CONNECTION</code></a>;
    </p><p>
      Message: Named pipe: %s
    </p></li><li class="listitem"><p><a name="error_cr_namedpipewait_error"></a>
      <a class="indexterm" name="idm46734184835984"></a>

      <a class="indexterm" name="idm46734184834944"></a>

      Error number: <code class="literal">2016</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_namedpipewait_error"><code class="literal">CR_NAMEDPIPEWAIT_ERROR</code></a>;
    </p><p>
      Message: Can't wait for named pipe to host: %s pipe: %s (%lu)
    </p></li><li class="listitem"><p><a name="error_cr_namedpipeopen_error"></a>
      <a class="indexterm" name="idm46734184829744"></a>

      <a class="indexterm" name="idm46734184828704"></a>

      Error number: <code class="literal">2017</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_namedpipeopen_error"><code class="literal">CR_NAMEDPIPEOPEN_ERROR</code></a>;
    </p><p>
      Message: Can't open named pipe to host: %s pipe: %s (%lu)
    </p></li><li class="listitem"><p><a name="error_cr_namedpipesetstate_error"></a>
      <a class="indexterm" name="idm46734184823520"></a>

      <a class="indexterm" name="idm46734184822480"></a>

      Error number: <code class="literal">2018</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_namedpipesetstate_error"><code class="literal">CR_NAMEDPIPESETSTATE_ERROR</code></a>;
    </p><p>
      Message: Can't set state of named pipe to host: %s pipe: %s (%lu)
    </p></li><li class="listitem"><p><a name="error_cr_cant_read_charset"></a>
      <a class="indexterm" name="idm46734184817200"></a>

      <a class="indexterm" name="idm46734184816160"></a>

      Error number: <code class="literal">2019</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_cant_read_charset"><code class="literal">CR_CANT_READ_CHARSET</code></a>;
    </p><p>
      Message: Can't initialize character set %s (path: %s)
    </p></li><li class="listitem"><p><a name="error_cr_net_packet_too_large"></a>
      <a class="indexterm" name="idm46734184810736"></a>

      <a class="indexterm" name="idm46734184809696"></a>

      Error number: <code class="literal">2020</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_net_packet_too_large"><code class="literal">CR_NET_PACKET_TOO_LARGE</code></a>;
    </p><p>
      Message: Got packet bigger than 'max_allowed_packet' bytes
    </p></li><li class="listitem"><p><a name="error_cr_embedded_connection"></a>
      <a class="indexterm" name="idm46734184804336"></a>

      <a class="indexterm" name="idm46734184803296"></a>

      Error number: <code class="literal">2021</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_embedded_connection"><code class="literal">CR_EMBEDDED_CONNECTION</code></a>;
    </p><p>
      Message: Embedded server
    </p></li><li class="listitem"><p><a name="error_cr_probe_slave_status"></a>
      <a class="indexterm" name="idm46734184798032"></a>

      <a class="indexterm" name="idm46734184796992"></a>

      Error number: <code class="literal">2022</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_probe_slave_status"><code class="literal">CR_PROBE_SLAVE_STATUS</code></a>;
    </p><p>
      Message: Error on SHOW SLAVE STATUS:
    </p></li><li class="listitem"><p><a name="error_cr_probe_slave_hosts"></a>
      <a class="indexterm" name="idm46734184791712"></a>

      <a class="indexterm" name="idm46734184790672"></a>

      Error number: <code class="literal">2023</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_probe_slave_hosts"><code class="literal">CR_PROBE_SLAVE_HOSTS</code></a>;
    </p><p>
      Message: Error on SHOW SLAVE HOSTS:
    </p></li><li class="listitem"><p><a name="error_cr_probe_slave_connect"></a>
      <a class="indexterm" name="idm46734184785328"></a>

      <a class="indexterm" name="idm46734184784288"></a>

      Error number: <code class="literal">2024</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_probe_slave_connect"><code class="literal">CR_PROBE_SLAVE_CONNECT</code></a>;
    </p><p>
      Message: Error connecting to slave:
    </p></li><li class="listitem"><p><a name="error_cr_probe_master_connect"></a>
      <a class="indexterm" name="idm46734184779008"></a>

      <a class="indexterm" name="idm46734184777968"></a>

      Error number: <code class="literal">2025</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_probe_master_connect"><code class="literal">CR_PROBE_MASTER_CONNECT</code></a>;
    </p><p>
      Message: Error connecting to master:
    </p></li><li class="listitem"><p><a name="error_cr_ssl_connection_error"></a>
      <a class="indexterm" name="idm46734184772624"></a>

      <a class="indexterm" name="idm46734184771584"></a>

      Error number: <code class="literal">2026</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_ssl_connection_error"><code class="literal">CR_SSL_CONNECTION_ERROR</code></a>;
    </p><p>
      Message: SSL connection error: %s
    </p></li><li class="listitem"><p><a name="error_cr_malformed_packet"></a>
      <a class="indexterm" name="idm46734184766304"></a>

      <a class="indexterm" name="idm46734184765264"></a>

      Error number: <code class="literal">2027</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_malformed_packet"><code class="literal">CR_MALFORMED_PACKET</code></a>;
    </p><p>
      Message: Malformed packet
    </p></li><li class="listitem"><p><a name="error_cr_wrong_license"></a>
      <a class="indexterm" name="idm46734184760048"></a>

      <a class="indexterm" name="idm46734184758992"></a>

      Error number: <code class="literal">2028</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_wrong_license"><code class="literal">CR_WRONG_LICENSE</code></a>;
    </p><p>
      Message: This client library is licensed only for use with MySQL
      servers having '%s' license
    </p></li><li class="listitem"><p><a name="error_cr_null_pointer"></a>
      <a class="indexterm" name="idm46734184753664"></a>

      <a class="indexterm" name="idm46734184752608"></a>

      Error number: <code class="literal">2029</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_null_pointer"><code class="literal">CR_NULL_POINTER</code></a>;
    </p><p>
      Message: Invalid use of null pointer
    </p></li><li class="listitem"><p><a name="error_cr_no_prepare_stmt"></a>
      <a class="indexterm" name="idm46734184747296"></a>

      <a class="indexterm" name="idm46734184746256"></a>

      Error number: <code class="literal">2030</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_no_prepare_stmt"><code class="literal">CR_NO_PREPARE_STMT</code></a>;
    </p><p>
      Message: Statement not prepared
    </p></li><li class="listitem"><p><a name="error_cr_params_not_bound"></a>
      <a class="indexterm" name="idm46734184740912"></a>

      <a class="indexterm" name="idm46734184739872"></a>

      Error number: <code class="literal">2031</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_params_not_bound"><code class="literal">CR_PARAMS_NOT_BOUND</code></a>;
    </p><p>
      Message: No data supplied for parameters in prepared statement
    </p></li><li class="listitem"><p><a name="error_cr_data_truncated"></a>
      <a class="indexterm" name="idm46734184734544"></a>

      <a class="indexterm" name="idm46734184733488"></a>

      Error number: <code class="literal">2032</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_data_truncated"><code class="literal">CR_DATA_TRUNCATED</code></a>;
    </p><p>
      Message: Data truncated
    </p></li><li class="listitem"><p><a name="error_cr_no_parameters_exists"></a>
      <a class="indexterm" name="idm46734184728192"></a>

      <a class="indexterm" name="idm46734184727152"></a>

      Error number: <code class="literal">2033</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_no_parameters_exists"><code class="literal">CR_NO_PARAMETERS_EXISTS</code></a>;
    </p><p>
      Message: No parameters exist in the statement
    </p></li><li class="listitem"><p><a name="error_cr_invalid_parameter_no"></a>
      <a class="indexterm" name="idm46734184721776"></a>

      <a class="indexterm" name="idm46734184720736"></a>

      Error number: <code class="literal">2034</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_invalid_parameter_no"><code class="literal">CR_INVALID_PARAMETER_NO</code></a>;
    </p><p>
      Message: Invalid parameter number
    </p><p>
      The column number for
      <a class="link" href="connectors-apis.html#mysql-stmt-fetch-column" title="27.7.10.12 mysql_stmt_fetch_column()"><code class="literal">mysql_stmt_fetch_column()</code></a> was
      invalid.
    </p><p>
      The parameter number for
      <a class="link" href="connectors-apis.html#mysql-stmt-send-long-data" title="27.7.10.26 mysql_stmt_send_long_data()"><code class="literal">mysql_stmt_send_long_data()</code></a> was
      invalid.
    </p><p>
      A key name was empty or the amount of connection attribute data
      for <a class="link" href="connectors-apis.html#mysql-options4" title="27.7.6.51 mysql_options4()"><code class="literal">mysql_options4()</code></a> exceeds the
      64KB limit.
    </p></li><li class="listitem"><p><a name="error_cr_invalid_buffer_use"></a>
      <a class="indexterm" name="idm46734184710416"></a>

      <a class="indexterm" name="idm46734184709376"></a>

      Error number: <code class="literal">2035</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_invalid_buffer_use"><code class="literal">CR_INVALID_BUFFER_USE</code></a>;
    </p><p>
      Message: Can't send long data for non-string/non-binary data types
      (parameter: %d)
    </p></li><li class="listitem"><p><a name="error_cr_unsupported_param_type"></a>
      <a class="indexterm" name="idm46734184704160"></a>

      <a class="indexterm" name="idm46734184703120"></a>

      Error number: <code class="literal">2036</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_unsupported_param_type"><code class="literal">CR_UNSUPPORTED_PARAM_TYPE</code></a>;
    </p><p>
      Message: Using unsupported buffer type: %d (parameter: %d)
    </p></li><li class="listitem"><p><a name="error_cr_shared_memory_connection"></a>
      <a class="indexterm" name="idm46734184697792"></a>

      <a class="indexterm" name="idm46734184696752"></a>

      Error number: <code class="literal">2037</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_shared_memory_connection"><code class="literal">CR_SHARED_MEMORY_CONNECTION</code></a>;
    </p><p>
      Message: Shared memory: %s
    </p></li><li class="listitem"><p><a name="error_cr_shared_memory_connect_request_error"></a>
      <a class="indexterm" name="idm46734184691408"></a>

      <a class="indexterm" name="idm46734184690368"></a>

      Error number: <code class="literal">2038</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_shared_memory_connect_request_error"><code class="literal">CR_SHARED_MEMORY_CONNECT_REQUEST_ERROR</code></a>;
    </p><p>
      Message: Can't open shared memory; client could not create request
      event (%lu)
    </p></li><li class="listitem"><p><a name="error_cr_shared_memory_connect_answer_error"></a>
      <a class="indexterm" name="idm46734184684864"></a>

      <a class="indexterm" name="idm46734184683824"></a>

      Error number: <code class="literal">2039</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_shared_memory_connect_answer_error"><code class="literal">CR_SHARED_MEMORY_CONNECT_ANSWER_ERROR</code></a>;
    </p><p>
      Message: Can't open shared memory; no answer event received from
      server (%lu)
    </p></li><li class="listitem"><p><a name="error_cr_shared_memory_connect_file_map_error"></a>
      <a class="indexterm" name="idm46734184678384"></a>

      <a class="indexterm" name="idm46734184677344"></a>

      Error number: <code class="literal">2040</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_shared_memory_connect_file_map_error"><code class="literal">CR_SHARED_MEMORY_CONNECT_FILE_MAP_ERROR</code></a>;
    </p><p>
      Message: Can't open shared memory; server could not allocate file
      mapping (%lu)
    </p></li><li class="listitem"><p><a name="error_cr_shared_memory_connect_map_error"></a>
      <a class="indexterm" name="idm46734184671904"></a>

      <a class="indexterm" name="idm46734184670864"></a>

      Error number: <code class="literal">2041</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_shared_memory_connect_map_error"><code class="literal">CR_SHARED_MEMORY_CONNECT_MAP_ERROR</code></a>;
    </p><p>
      Message: Can't open shared memory; server could not get pointer to
      file mapping (%lu)
    </p></li><li class="listitem"><p><a name="error_cr_shared_memory_file_map_error"></a>
      <a class="indexterm" name="idm46734184665472"></a>

      <a class="indexterm" name="idm46734184664368"></a>

      Error number: <code class="literal">2042</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_shared_memory_file_map_error"><code class="literal">CR_SHARED_MEMORY_FILE_MAP_ERROR</code></a>;
    </p><p>
      Message: Can't open shared memory; client could not allocate file
      mapping (%lu)
    </p></li><li class="listitem"><p><a name="error_cr_shared_memory_map_error"></a>
      <a class="indexterm" name="idm46734184658992"></a>

      <a class="indexterm" name="idm46734184657952"></a>

      Error number: <code class="literal">2043</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_shared_memory_map_error"><code class="literal">CR_SHARED_MEMORY_MAP_ERROR</code></a>;
    </p><p>
      Message: Can't open shared memory; client could not get pointer to
      file mapping (%lu)
    </p></li><li class="listitem"><p><a name="error_cr_shared_memory_event_error"></a>
      <a class="indexterm" name="idm46734184652528"></a>

      <a class="indexterm" name="idm46734184651488"></a>

      Error number: <code class="literal">2044</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_shared_memory_event_error"><code class="literal">CR_SHARED_MEMORY_EVENT_ERROR</code></a>;
    </p><p>
      Message: Can't open shared memory; client could not create %s
      event (%lu)
    </p></li><li class="listitem"><p><a name="error_cr_shared_memory_connect_abandoned_error"></a>
      <a class="indexterm" name="idm46734184646080"></a>

      <a class="indexterm" name="idm46734184645040"></a>

      Error number: <code class="literal">2045</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_shared_memory_connect_abandoned_error"><code class="literal">CR_SHARED_MEMORY_CONNECT_ABANDONED_ERROR</code></a>;
    </p><p>
      Message: Can't open shared memory; no answer from server (%lu)
    </p></li><li class="listitem"><p><a name="error_cr_shared_memory_connect_set_error"></a>
      <a class="indexterm" name="idm46734184639584"></a>

      <a class="indexterm" name="idm46734184638544"></a>

      Error number: <code class="literal">2046</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_shared_memory_connect_set_error"><code class="literal">CR_SHARED_MEMORY_CONNECT_SET_ERROR</code></a>;
    </p><p>
      Message: Can't open shared memory; cannot send request event to
      server (%lu)
    </p></li><li class="listitem"><p><a name="error_cr_conn_unknow_protocol"></a>
      <a class="indexterm" name="idm46734184633088"></a>

      <a class="indexterm" name="idm46734184632048"></a>

      Error number: <code class="literal">2047</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_conn_unknow_protocol"><code class="literal">CR_CONN_UNKNOW_PROTOCOL</code></a>;
    </p><p>
      Message: Wrong or unknown protocol
    </p></li><li class="listitem"><p><a name="error_cr_invalid_conn_handle"></a>
      <a class="indexterm" name="idm46734184626816"></a>

      <a class="indexterm" name="idm46734184625776"></a>

      Error number: <code class="literal">2048</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_invalid_conn_handle"><code class="literal">CR_INVALID_CONN_HANDLE</code></a>;
    </p><p>
      Message: Invalid connection handle
    </p></li><li class="listitem"><p><a name="error_cr_secure_auth"></a>
      <a class="indexterm" name="idm46734184620544"></a>

      <a class="indexterm" name="idm46734184619488"></a>

      Error number: <code class="literal">2049</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_secure_auth"><code class="literal">CR_SECURE_AUTH</code></a>;
    </p><p>
      Message: Connection using old (pre-4.1.1) authentication protocol
      refused (client option 'secure_auth' enabled)
    </p><p>
      <a class="link" href="error-handling.html#error_cr_secure_auth"><code class="literal">CR_SECURE_AUTH</code></a> was removed after
      5.7.4.
    </p></li><li class="listitem"><p><a name="error_cr_unused_1"></a>
      <a class="indexterm" name="idm46734184612512"></a>

      <a class="indexterm" name="idm46734184611472"></a>

      Error number: <code class="literal">2049</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_unused_1"><code class="literal">CR_UNUSED_1</code></a>;
    </p><p>
      Message: Connection using old (pre-4.1.1) authentication protocol
      refused (client option 'secure_auth' enabled)
    </p><p>
      <a class="link" href="error-handling.html#error_cr_unused_1"><code class="literal">CR_UNUSED_1</code></a> was added in 5.7.5.
    </p></li><li class="listitem"><p><a name="error_cr_fetch_canceled"></a>
      <a class="indexterm" name="idm46734184604496"></a>

      <a class="indexterm" name="idm46734184603440"></a>

      Error number: <code class="literal">2050</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_fetch_canceled"><code class="literal">CR_FETCH_CANCELED</code></a>;
    </p><p>
      Message: Row retrieval was canceled by mysql_stmt_close() call
    </p></li><li class="listitem"><p><a name="error_cr_no_data"></a>
      <a class="indexterm" name="idm46734184598256"></a>

      <a class="indexterm" name="idm46734184597216"></a>

      Error number: <code class="literal">2051</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_no_data"><code class="literal">CR_NO_DATA</code></a>;
    </p><p>
      Message: Attempt to read column without prior row fetch
    </p></li><li class="listitem"><p><a name="error_cr_no_stmt_metadata"></a>
      <a class="indexterm" name="idm46734184591952"></a>

      <a class="indexterm" name="idm46734184590912"></a>

      Error number: <code class="literal">2052</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_no_stmt_metadata"><code class="literal">CR_NO_STMT_METADATA</code></a>;
    </p><p>
      Message: Prepared statement contains no metadata
    </p></li><li class="listitem"><p><a name="error_cr_no_result_set"></a>
      <a class="indexterm" name="idm46734184585600"></a>

      <a class="indexterm" name="idm46734184584544"></a>

      Error number: <code class="literal">2053</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_no_result_set"><code class="literal">CR_NO_RESULT_SET</code></a>;
    </p><p>
      Message: Attempt to read a row while there is no result set
      associated with the statement
    </p></li><li class="listitem"><p><a name="error_cr_not_implemented"></a>
      <a class="indexterm" name="idm46734184579168"></a>

      <a class="indexterm" name="idm46734184578128"></a>

      Error number: <code class="literal">2054</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_not_implemented"><code class="literal">CR_NOT_IMPLEMENTED</code></a>;
    </p><p>
      Message: This feature is not implemented yet
    </p></li><li class="listitem"><p><a name="error_cr_server_lost_extended"></a>
      <a class="indexterm" name="idm46734184572832"></a>

      <a class="indexterm" name="idm46734184571792"></a>

      Error number: <code class="literal">2055</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_server_lost_extended"><code class="literal">CR_SERVER_LOST_EXTENDED</code></a>;
    </p><p>
      Message: Lost connection to MySQL server at '%s', system error: %d
    </p></li><li class="listitem"><p><a name="error_cr_stmt_closed"></a>
      <a class="indexterm" name="idm46734184566464"></a>

      <a class="indexterm" name="idm46734184565408"></a>

      Error number: <code class="literal">2056</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_stmt_closed"><code class="literal">CR_STMT_CLOSED</code></a>;
    </p><p>
      Message: Statement closed indirectly because of a preceding %s()
      call
    </p></li><li class="listitem"><p><a name="error_cr_new_stmt_metadata"></a>
      <a class="indexterm" name="idm46734184560064"></a>

      <a class="indexterm" name="idm46734184559024"></a>

      Error number: <code class="literal">2057</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_new_stmt_metadata"><code class="literal">CR_NEW_STMT_METADATA</code></a>;
    </p><p>
      Message: The number of columns in the result set differs from the
      number of bound buffers. You must reset the statement, rebind the
      result set columns, and execute the statement again
    </p></li><li class="listitem"><p><a name="error_cr_already_connected"></a>
      <a class="indexterm" name="idm46734184553504"></a>

      <a class="indexterm" name="idm46734184552464"></a>

      Error number: <code class="literal">2058</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_already_connected"><code class="literal">CR_ALREADY_CONNECTED</code></a>;
    </p><p>
      Message: This handle is already connected. Use a separate handle
      for each connection.
    </p></li><li class="listitem"><p><a name="error_cr_auth_plugin_cannot_load"></a>
      <a class="indexterm" name="idm46734184547200"></a>

      <a class="indexterm" name="idm46734184546160"></a>

      Error number: <code class="literal">2059</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_auth_plugin_cannot_load"><code class="literal">CR_AUTH_PLUGIN_CANNOT_LOAD</code></a>;
    </p><p>
      Message: Authentication plugin '%s' cannot be loaded: %s
    </p></li><li class="listitem"><p><a name="error_cr_duplicate_connection_attr"></a>
      <a class="indexterm" name="idm46734184540816"></a>

      <a class="indexterm" name="idm46734184539776"></a>

      Error number: <code class="literal">2060</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_duplicate_connection_attr"><code class="literal">CR_DUPLICATE_CONNECTION_ATTR</code></a>;
    </p><p>
      Message: There is an attribute with the same name already
    </p><p>
      A duplicate connection attribute name was specified for
      <a class="link" href="connectors-apis.html#mysql-options4" title="27.7.6.51 mysql_options4()"><code class="literal">mysql_options4()</code></a>.
    </p></li><li class="listitem"><p><a name="error_cr_auth_plugin_err"></a>
      <a class="indexterm" name="idm46734184532752"></a>

      <a class="indexterm" name="idm46734184531712"></a>

      Error number: <code class="literal">2061</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_auth_plugin_err"><code class="literal">CR_AUTH_PLUGIN_ERR</code></a>;
    </p><p>
      Message: Authentication plugin '%s' reported error: %s
    </p><p>
      <a class="link" href="error-handling.html#error_cr_auth_plugin_err"><code class="literal">CR_AUTH_PLUGIN_ERR</code></a> was added in
      5.7.1.
    </p></li><li class="listitem"><p><a name="error_cr_insecure_api_err"></a>
      <a class="indexterm" name="idm46734184524736"></a>

      <a class="indexterm" name="idm46734184523696"></a>

      Error number: <code class="literal">2062</code>; Symbol:
      <a class="link" href="error-handling.html#error_cr_insecure_api_err"><code class="literal">CR_INSECURE_API_ERR</code></a>;
    </p><p>
      Message: Insecure API function call: '%s' Use instead: '%s'
    </p><p>
      An insecure function call was detected. Modify the application to
      use the suggested alternative function instead.
    </p><p>
      <a class="link" href="error-handling.html#error_cr_insecure_api_err"><code class="literal">CR_INSECURE_API_ERR</code></a> was added in
      5.7.6.
</p></li></ul>
</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="global-error-reference"></a>B.3.3 Global Error Message Reference</h3>

</div>

</div>

</div>
<p>
        This section lists global error messages that are shared in the
        sense that they can be produced by the MySQL server or by MySQL
        client programs. These errors have error codes in the range from
        1 to 999.
      </p><p>
        Each global error message includes an error code, SQLSTATE
        value, and message string, as described in
        <a class="xref" href="error-handling.html#error-message-components" title="B.1 Error Message Sources and Components">Section B.1, “Error Message Sources and Components”</a>. These components are
        available as described in <a class="xref" href="error-handling.html#error-interfaces" title="B.2 Error Information Interfaces">Section B.2, “Error Information Interfaces”</a>.
        For global errors, the SQLSTATE value is always
        <code class="literal">'HY000'</code> (general error), so it is not
        meaningful for distinguishing one client error from another.
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><a name="error_ee_cantcreatefile"></a>
      <a class="indexterm" name="idm46734184510512"></a>

      <a class="indexterm" name="idm46734184509456"></a>

      Error number: <code class="literal">1</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_cantcreatefile"><code class="literal">EE_CANTCREATEFILE</code></a>;
    </p><p>
      Message: Can't create/write to file '%s' (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_read"></a>
      <a class="indexterm" name="idm46734184504208"></a>

      <a class="indexterm" name="idm46734184503168"></a>

      Error number: <code class="literal">2</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_read"><code class="literal">EE_READ</code></a>;
    </p><p>
      Message: Error reading file '%s' (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_write"></a>
      <a class="indexterm" name="idm46734184497984"></a>

      <a class="indexterm" name="idm46734184496944"></a>

      Error number: <code class="literal">3</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_write"><code class="literal">EE_WRITE</code></a>;
    </p><p>
      Message: Error writing file '%s' (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_badclose"></a>
      <a class="indexterm" name="idm46734184491696"></a>

      <a class="indexterm" name="idm46734184490656"></a>

      Error number: <code class="literal">4</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_badclose"><code class="literal">EE_BADCLOSE</code></a>;
    </p><p>
      Message: Error on close of '%s' (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_outofmemory"></a>
      <a class="indexterm" name="idm46734184485408"></a>

      <a class="indexterm" name="idm46734184484352"></a>

      Error number: <code class="literal">5</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_outofmemory"><code class="literal">EE_OUTOFMEMORY</code></a>;
    </p><p>
      Message: Out of memory (Needed %u bytes)
    </p></li><li class="listitem"><p><a name="error_ee_delete"></a>
      <a class="indexterm" name="idm46734184479120"></a>

      <a class="indexterm" name="idm46734184478080"></a>

      Error number: <code class="literal">6</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_delete"><code class="literal">EE_DELETE</code></a>;
    </p><p>
      Message: Error on delete of '%s' (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_link"></a>
      <a class="indexterm" name="idm46734184472832"></a>

      <a class="indexterm" name="idm46734184471792"></a>

      Error number: <code class="literal">7</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_link"><code class="literal">EE_LINK</code></a>;
    </p><p>
      Message: Error on rename of '%s' to '%s' (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_eoferr"></a>
      <a class="indexterm" name="idm46734184466480"></a>

      <a class="indexterm" name="idm46734184465440"></a>

      Error number: <code class="literal">9</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_eoferr"><code class="literal">EE_EOFERR</code></a>;
    </p><p>
      Message: Unexpected EOF found when reading file '%s' (Errcode: %d
      - %s)
    </p></li><li class="listitem"><p><a name="error_ee_cantlock"></a>
      <a class="indexterm" name="idm46734184460224"></a>

      <a class="indexterm" name="idm46734184459184"></a>

      Error number: <code class="literal">10</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_cantlock"><code class="literal">EE_CANTLOCK</code></a>;
    </p><p>
      Message: Can't lock file (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_cantunlock"></a>
      <a class="indexterm" name="idm46734184453952"></a>

      <a class="indexterm" name="idm46734184452896"></a>

      Error number: <code class="literal">11</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_cantunlock"><code class="literal">EE_CANTUNLOCK</code></a>;
    </p><p>
      Message: Can't unlock file (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_dir"></a>
      <a class="indexterm" name="idm46734184447584"></a>

      <a class="indexterm" name="idm46734184446544"></a>

      Error number: <code class="literal">12</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_dir"><code class="literal">EE_DIR</code></a>;
    </p><p>
      Message: Can't read dir of '%s' (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_stat"></a>
      <a class="indexterm" name="idm46734184441296"></a>

      <a class="indexterm" name="idm46734184440256"></a>

      Error number: <code class="literal">13</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_stat"><code class="literal">EE_STAT</code></a>;
    </p><p>
      Message: Can't get stat of '%s' (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_cant_chsize"></a>
      <a class="indexterm" name="idm46734184435008"></a>

      <a class="indexterm" name="idm46734184433952"></a>

      Error number: <code class="literal">14</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_cant_chsize"><code class="literal">EE_CANT_CHSIZE</code></a>;
    </p><p>
      Message: Can't change size of file (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_cant_open_stream"></a>
      <a class="indexterm" name="idm46734184428720"></a>

      <a class="indexterm" name="idm46734184427680"></a>

      Error number: <code class="literal">15</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_cant_open_stream"><code class="literal">EE_CANT_OPEN_STREAM</code></a>;
    </p><p>
      Message: Can't open stream from handle (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_getwd"></a>
      <a class="indexterm" name="idm46734184422400"></a>

      <a class="indexterm" name="idm46734184421360"></a>

      Error number: <code class="literal">16</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_getwd"><code class="literal">EE_GETWD</code></a>;
    </p><p>
      Message: Can't get working directory (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_setwd"></a>
      <a class="indexterm" name="idm46734184416176"></a>

      <a class="indexterm" name="idm46734184415136"></a>

      Error number: <code class="literal">17</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_setwd"><code class="literal">EE_SETWD</code></a>;
    </p><p>
      Message: Can't change dir to '%s' (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_link_warning"></a>
      <a class="indexterm" name="idm46734184409888"></a>

      <a class="indexterm" name="idm46734184408832"></a>

      Error number: <code class="literal">18</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_link_warning"><code class="literal">EE_LINK_WARNING</code></a>;
    </p><p>
      Message: Warning: '%s' had %d links
    </p></li><li class="listitem"><p><a name="error_ee_open_warning"></a>
      <a class="indexterm" name="idm46734184403536"></a>

      <a class="indexterm" name="idm46734184402480"></a>

      Error number: <code class="literal">19</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_open_warning"><code class="literal">EE_OPEN_WARNING</code></a>;
    </p><p>
      Message: Warning: %d files and %d streams is left open
    </p></li><li class="listitem"><p><a name="error_ee_disk_full"></a>
      <a class="indexterm" name="idm46734184397296"></a>

      <a class="indexterm" name="idm46734184396256"></a>

      Error number: <code class="literal">20</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_disk_full"><code class="literal">EE_DISK_FULL</code></a>;
    </p><p>
      Message: Disk is full writing '%s' (Errcode: %d - %s). Waiting for
      someone to free space...
    </p></li><li class="listitem"><p><a name="error_ee_cant_mkdir"></a>
      <a class="indexterm" name="idm46734184390896"></a>

      <a class="indexterm" name="idm46734184389840"></a>

      Error number: <code class="literal">21</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_cant_mkdir"><code class="literal">EE_CANT_MKDIR</code></a>;
    </p><p>
      Message: Can't create directory '%s' (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_unknown_charset"></a>
      <a class="indexterm" name="idm46734184384608"></a>

      <a class="indexterm" name="idm46734184383568"></a>

      Error number: <code class="literal">22</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_unknown_charset"><code class="literal">EE_UNKNOWN_CHARSET</code></a>;
    </p><p>
      Message: Character set '%s' is not a compiled character set and is
      not specified in the '%s' file
    </p></li><li class="listitem"><p><a name="error_ee_out_of_fileresources"></a>
      <a class="indexterm" name="idm46734184378192"></a>

      <a class="indexterm" name="idm46734184377152"></a>

      Error number: <code class="literal">23</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_out_of_fileresources"><code class="literal">EE_OUT_OF_FILERESOURCES</code></a>;
    </p><p>
      Message: Out of resources when opening file '%s' (Errcode: %d -
      %s)
    </p></li><li class="listitem"><p><a name="error_ee_cant_readlink"></a>
      <a class="indexterm" name="idm46734184371920"></a>

      <a class="indexterm" name="idm46734184370864"></a>

      Error number: <code class="literal">24</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_cant_readlink"><code class="literal">EE_CANT_READLINK</code></a>;
    </p><p>
      Message: Can't read value for symlink '%s' (Error %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_cant_symlink"></a>
      <a class="indexterm" name="idm46734184365616"></a>

      <a class="indexterm" name="idm46734184364560"></a>

      Error number: <code class="literal">25</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_cant_symlink"><code class="literal">EE_CANT_SYMLINK</code></a>;
    </p><p>
      Message: Can't create symlink '%s' pointing at '%s' (Error %d -
      %s)
    </p></li><li class="listitem"><p><a name="error_ee_realpath"></a>
      <a class="indexterm" name="idm46734184359296"></a>

      <a class="indexterm" name="idm46734184358256"></a>

      Error number: <code class="literal">26</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_realpath"><code class="literal">EE_REALPATH</code></a>;
    </p><p>
      Message: Error on realpath() on '%s' (Error %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_sync"></a>
      <a class="indexterm" name="idm46734184353072"></a>

      <a class="indexterm" name="idm46734184352032"></a>

      Error number: <code class="literal">27</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_sync"><code class="literal">EE_SYNC</code></a>;
    </p><p>
      Message: Can't sync file '%s' to disk (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_unknown_collation"></a>
      <a class="indexterm" name="idm46734184346672"></a>

      <a class="indexterm" name="idm46734184345632"></a>

      Error number: <code class="literal">28</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_unknown_collation"><code class="literal">EE_UNKNOWN_COLLATION</code></a>;
    </p><p>
      Message: Collation '%s' is not a compiled collation and is not
      specified in the '%s' file
    </p></li><li class="listitem"><p><a name="error_ee_filenotfound"></a>
      <a class="indexterm" name="idm46734184340240"></a>

      <a class="indexterm" name="idm46734184339184"></a>

      Error number: <code class="literal">29</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_filenotfound"><code class="literal">EE_FILENOTFOUND</code></a>;
    </p><p>
      Message: File '%s' not found (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_file_not_closed"></a>
      <a class="indexterm" name="idm46734184333952"></a>

      <a class="indexterm" name="idm46734184332912"></a>

      Error number: <code class="literal">30</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_file_not_closed"><code class="literal">EE_FILE_NOT_CLOSED</code></a>;
    </p><p>
      Message: File '%s' (fileno: %d) was not closed
    </p></li><li class="listitem"><p><a name="error_ee_change_ownership"></a>
      <a class="indexterm" name="idm46734184327520"></a>

      <a class="indexterm" name="idm46734184326480"></a>

      Error number: <code class="literal">31</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_change_ownership"><code class="literal">EE_CHANGE_OWNERSHIP</code></a>;
    </p><p>
      Message: Can't change ownership of the file '%s' (Errcode: %d -
      %s)
    </p></li><li class="listitem"><p><a name="error_ee_change_permissions"></a>
      <a class="indexterm" name="idm46734184321136"></a>

      <a class="indexterm" name="idm46734184320096"></a>

      Error number: <code class="literal">32</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_change_permissions"><code class="literal">EE_CHANGE_PERMISSIONS</code></a>;
    </p><p>
      Message: Can't change permissions of the file '%s' (Errcode: %d -
      %s)
    </p></li><li class="listitem"><p><a name="error_ee_cant_seek"></a>
      <a class="indexterm" name="idm46734184314800"></a>

      <a class="indexterm" name="idm46734184313760"></a>

      Error number: <code class="literal">33</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_cant_seek"><code class="literal">EE_CANT_SEEK</code></a>;
    </p><p>
      Message: Can't seek in file '%s' (Errcode: %d - %s)
    </p></li><li class="listitem"><p><a name="error_ee_capacity_exceeded"></a>
      <a class="indexterm" name="idm46734184308464"></a>

      <a class="indexterm" name="idm46734184307424"></a>

      Error number: <code class="literal">34</code>; Symbol:
      <a class="link" href="error-handling.html#error_ee_capacity_exceeded"><code class="literal">EE_CAPACITY_EXCEEDED</code></a>;
    </p><p>
      Message: Memory capacity exceeded (capacity %llu bytes)
    </p><p>
      <a class="link" href="error-handling.html#error_ee_capacity_exceeded"><code class="literal">EE_CAPACITY_EXCEEDED</code></a> was added in
      5.7.9.
</p></li></ul>
</div>

</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h2 class="title" style="clear: both"><a name="problems"></a>B.4 Problems and Common Errors</h2>

</div>

</div>

</div>
<div class="toc">
<dl class="toc"><dt><span class="section"><a href="error-handling.html#what-is-crashing">B.4.1 How to Determine What Is Causing a Problem</a></span></dt><dt><span class="section"><a href="error-handling.html#common-errors">B.4.2 Common Errors When Using MySQL Programs</a></span></dt><dt><span class="section"><a href="error-handling.html#administration-issues">B.4.3 Administration-Related Issues</a></span></dt><dt><span class="section"><a href="error-handling.html#query-issues">B.4.4 Query-Related Issues</a></span></dt><dt><span class="section"><a href="error-handling.html#optimizer-issues">B.4.5 Optimizer-Related Issues</a></span></dt><dt><span class="section"><a href="error-handling.html#table-definition-issues">B.4.6 Table Definition-Related Issues</a></span></dt><dt><span class="section"><a href="error-handling.html#known-issues">B.4.7 Known Issues in MySQL</a></span></dt></dl>
</div>
<a class="indexterm" name="idm46734184299904"></a><a class="indexterm" name="idm46734184298448"></a><p>
      This section lists some common problems and error messages that
      you may encounter. It describes how to determine the causes of the
      problems and what to do to solve them.
</p>
<div class="section">

<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="what-is-crashing"></a>B.4.1 How to Determine What Is Causing a Problem</h3>
</div>
</div>
</div>
<p>
        When you run into a problem, the first thing you should do is to
        find out which program or piece of equipment is causing it:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
            If you have one of the following symptoms, then it is
            probably a hardware problems (such as memory, motherboard,
            CPU, or hard disk) or kernel problem:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p>
                The keyboard does not work. This can normally be checked
                by pressing the Caps Lock key. If the Caps Lock light
                does not change, you have to replace your keyboard.
                (Before doing this, you should try to restart your
                computer and check all cables to the keyboard.)
              </p></li><li class="listitem"><p>
                The mouse pointer does not move.
              </p></li><li class="listitem"><p>
                The machine does not answer to a remote machine's pings.
              </p></li><li class="listitem"><p>
                Other programs that are not related to MySQL do not
                behave correctly.
              </p></li><li class="listitem"><p>
                Your system restarted unexpectedly. (A faulty user-level
                program should never be able to take down your system.)
</p></li></ul>
</div>
<p>
            In this case, you should start by checking all your cables
            and run some diagnostic tool to check your hardware! You
            should also check whether there are any patches, updates, or
            service packs for your operating system that could likely
            solve your problem. Check also that all your libraries (such
            as <code class="literal">glibc</code>) are up to date.
          </p><p>
            It is always good to use a machine with ECC memory to
            discover memory problems early.
          </p></li><li class="listitem"><p>
            If your keyboard is locked up, you may be able to recover by
            logging in to your machine from another machine and
            executing <code class="literal">kbd_mode -a</code>.
          </p></li><li class="listitem"><p>
            Please examine your system log file
            (<code class="filename">/var/log/messages</code> or similar) for
            reasons for your problem. If you think the problem is in
            MySQL, you should also examine MySQL's log files. See
            <a class="xref" href="server-administration.html#server-logs" title="5.4 MySQL Server Logs">Section 5.4, “MySQL Server Logs”</a>.
          </p></li><li class="listitem"><p>
            If you do not think you have hardware problems, you should
            try to find out which program is causing problems. Try using
            <span class="command"><strong>top</strong></span>, <span class="command"><strong>ps</strong></span>, Task Manager,
            or some similar program, to check which program is taking
            all CPU or is locking the machine.
          </p></li><li class="listitem"><p>
            Use <span class="command"><strong>top</strong></span>, <span class="command"><strong>df</strong></span>, or a
            similar program to check whether you are out of memory, disk
            space, file descriptors, or some other critical resource.
          </p></li><li class="listitem"><p>
            If the problem is some runaway process, you can always try
            to kill it. If it does not want to die, there is probably a
            bug in the operating system.
</p></li></ul>
</div>
<p>
        If you have examined all other possibilities and concluded that
        the MySQL server or a MySQL client is causing the problem, it is
        time to create a bug report, see <a class="xref" href="introduction.html#bug-reports" title="1.7 How to Report Bugs or Problems">Section 1.7, “How to Report Bugs or Problems”</a>.
        In the bug report, try to give a complete description of how the
        system is behaving and what you think is happening. Also state
        why you think that MySQL is causing the problem. Take into
        consideration all the situations described in this chapter.
        State any problems exactly how they appear when you examine your
        system. Use the <span class="quote">“<span class="quote">copy and paste</span>”</span> method for any
        output and error messages from programs and log files.
      </p><p>
        Try to describe in detail which program is not working and all
        symptoms you see. We have in the past received many bug reports
        that state only <span class="quote">“<span class="quote">the system does not work.</span>”</span> This
        provides us with no information about what could be the problem.
      </p><p>
        If a program fails, it is always useful to know the following
        information:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
            Has the program in question made a segmentation fault (did
            it dump core)?
          </p></li><li class="listitem"><p>
            Is the program taking up all available CPU time? Check with
            <span class="command"><strong>top</strong></span>. Let the program run for a while, it
            may simply be evaluating something computationally
            intensive.
          </p></li><li class="listitem"><p>
            If the <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> server is causing problems,
            can you get any response from it with <a class="link" href="programs.html#mysqladmin" title="4.5.2 mysqladmin — Client for Administering a MySQL Server"><span class="command"><strong>mysqladmin -u
            root ping</strong></span></a> or <a class="link" href="programs.html#mysqladmin" title="4.5.2 mysqladmin — Client for Administering a MySQL Server"><span class="command"><strong>mysqladmin -u root
            processlist</strong></span></a>?
          </p></li><li class="listitem"><p>
            What does a client program say when you try to connect to
            the MySQL server? (Try with <a class="link" href="programs.html#mysql" title="4.5.1 mysql — The MySQL Command-Line Client"><span class="command"><strong>mysql</strong></span></a>, for
            example.) Does the client jam? Do you get any output from
            the program?
</p></li></ul>
</div>
<p>
        When sending a bug report, you should follow the outline
        described in <a class="xref" href="introduction.html#bug-reports" title="1.7 How to Report Bugs or Problems">Section 1.7, “How to Report Bugs or Problems”</a>.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="common-errors"></a>B.4.2 Common Errors When Using MySQL Programs</h3>

</div>

</div>

</div>
<div class="toc">
<dl class="toc"><dt><span class="section"><a href="error-handling.html#error-access-denied">B.4.2.1 Access denied</a></span></dt><dt><span class="section"><a href="error-handling.html#can-not-connect-to-server">B.4.2.2 Can't connect to [local] MySQL server</a></span></dt><dt><span class="section"><a href="error-handling.html#error-lost-connection">B.4.2.3 Lost connection to MySQL server</a></span></dt><dt><span class="section"><a href="error-handling.html#password-too-long">B.4.2.4 Password Fails When Entered Interactively</a></span></dt><dt><span class="section"><a href="error-handling.html#blocked-host">B.4.2.5 Host 'host_name' is blocked</a></span></dt><dt><span class="section"><a href="error-handling.html#too-many-connections">B.4.2.6 Too many connections</a></span></dt><dt><span class="section"><a href="error-handling.html#out-of-memory">B.4.2.7 Out of memory</a></span></dt><dt><span class="section"><a href="error-handling.html#gone-away">B.4.2.8 MySQL server has gone away</a></span></dt><dt><span class="section"><a href="error-handling.html#packet-too-large">B.4.2.9 Packet Too Large</a></span></dt><dt><span class="section"><a href="error-handling.html#communication-errors">B.4.2.10 Communication Errors and Aborted Connections</a></span></dt><dt><span class="section"><a href="error-handling.html#full-table">B.4.2.11 The table is full</a></span></dt><dt><span class="section"><a href="error-handling.html#cannot-create">B.4.2.12 Can't create/write to file</a></span></dt><dt><span class="section"><a href="error-handling.html#commands-out-of-sync">B.4.2.13 Commands out of sync</a></span></dt><dt><span class="section"><a href="error-handling.html#ignoring-user">B.4.2.14 Ignoring user</a></span></dt><dt><span class="section"><a href="error-handling.html#cannot-find-table">B.4.2.15 Table 'tbl_name' doesn't exist</a></span></dt><dt><span class="section"><a href="error-handling.html#cannot-initialize-character-set">B.4.2.16 Can't initialize character set</a></span></dt><dt><span class="section"><a href="error-handling.html#not-enough-file-handles">B.4.2.17 File Not Found and Similar Errors</a></span></dt><dt><span class="section"><a href="error-handling.html#table-corruption">B.4.2.18 Table-Corruption Issues</a></span></dt></dl>
</div>
<a class="indexterm" name="idm46734184260480"></a><p>
        This section lists some errors that users frequently encounter
        when running MySQL programs. Although the problems show up when
        you try to run client programs, the solutions to many of the
        problems involves changing the configuration of the MySQL
        server.
</p>
<div class="section">

<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="error-access-denied"></a>B.4.2.1 Access denied</h4>
</div>
</div>
</div>
<a class="indexterm" name="idm46734184257232"></a><a class="indexterm" name="idm46734184255744"></a><a class="indexterm" name="idm46734184254256"></a><p>
          An <code class="literal">Access denied</code> error can have many
          causes. Often the problem is related to the MySQL accounts
          that the server permits client programs to use when
          connecting. See <a class="xref" href="security.html#access-control" title="6.2 Access Control and Account Management">Section 6.2, “Access Control and Account Management”</a>, and
          <a class="xref" href="security.html#problems-connecting" title="6.2.17 Troubleshooting Problems Connecting to MySQL">Section 6.2.17, “Troubleshooting Problems Connecting to MySQL”</a>.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="can-not-connect-to-server"></a>B.4.2.2 Can't connect to [local] MySQL server</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734184249216"></a><a class="indexterm" name="idm46734184248144"></a><p>
          A MySQL client on Unix can connect to the
          <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> server in two different ways: By
          using a Unix socket file to connect through a file in the file
          system (default <code class="filename">/tmp/mysql.sock</code>), or by
          using TCP/IP, which connects through a port number. A Unix
          socket file connection is faster than TCP/IP, but can be used
          only when connecting to a server on the same computer. A Unix
          socket file is used if you do not specify a host name or if
          you specify the special host name
          <code class="literal">localhost</code>.
        </p><p>
          If the MySQL server is running on Windows, you can connect
          using TCP/IP. If the server is started with the
          <a class="link" href="server-administration.html#sysvar_named_pipe"><code class="literal">named_pipe</code></a> system variable
          enabled, you can also connect with named pipes if you run the
          client on the host where the server is running. The name of
          the named pipe is <code class="literal">MySQL</code> by default. If you
          do not give a host name when connecting to
          <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>, a MySQL client first tries to
          connect to the named pipe. If that does not work, it connects
          to the TCP/IP port. You can force the use of named pipes on
          Windows by using <code class="literal">.</code> as the host name.
        </p><p>
          The error (2002) <code class="literal">Can't connect to ...</code>
          normally means that there is no MySQL server running on the
          system or that you are using an incorrect Unix socket file
          name or TCP/IP port number when trying to connect to the
          server. You should also check that the TCP/IP port you are
          using has not been blocked by a firewall or port blocking
          service.
        </p><p>
          The error (2003) <code class="literal">Can't connect to MySQL server on
          '<em class="replaceable"><code>server</code></em>' (10061)</code>
          indicates that the network connection has been refused. You
          should check that there is a MySQL server running, that it has
          network connections enabled, and that the network port you
          specified is the one configured on the server.
        </p><p>
          Start by checking whether there is a process named
          <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> running on your server host. (Use
          <span class="command"><strong>ps xa | grep mysqld</strong></span> on Unix or the Task
          Manager on Windows.) If there is no such process, you should
          start the server. See <a class="xref" href="installing.html#starting-server" title="2.10.2 Starting the Server">Section 2.10.2, “Starting the Server”</a>.
        </p><p>
          If a <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> process is running, you can
          check it by trying the following commands. The port number or
          Unix socket file name might be different in your setup.
          <code class="literal">host_ip</code> represents the IP address of the
          machine where the server is running.
        </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>mysqladmin version</code></strong>
shell&gt; <strong class="userinput"><code>mysqladmin variables</code></strong>
shell&gt; <strong class="userinput"><code>mysqladmin -h `hostname` version variables</code></strong>
shell&gt; <strong class="userinput"><code>mysqladmin -h `hostname` --port=3306 version</code></strong>
shell&gt; <strong class="userinput"><code>mysqladmin -h host_ip version</code></strong>
shell&gt; <strong class="userinput"><code>mysqladmin --protocol=SOCKET --socket=/tmp/mysql.sock version</code></strong>
</pre><p>
          Note the use of backticks rather than forward quotation marks
          with the <span class="command"><strong>hostname</strong></span> command; these cause the
          output of <span class="command"><strong>hostname</strong></span> (that is, the current
          host name) to be substituted into the
          <a class="link" href="programs.html#mysqladmin" title="4.5.2 mysqladmin — Client for Administering a MySQL Server"><span class="command"><strong>mysqladmin</strong></span></a> command. If you have no
          <span class="command"><strong>hostname</strong></span> command or are running on Windows,
          you can manually type the host name of your machine (without
          backticks) following the <code class="literal">-h</code> option. You can
          also try <code class="literal">-h 127.0.0.1</code> to connect with
          TCP/IP to the local host.
        </p><p>
          Make sure that the server has not been configured to ignore
          network connections or (if you are attempting to connect
          remotely) that it has not been configured to listen only
          locally on its network interfaces. If the server was started
          with the <a class="link" href="server-administration.html#sysvar_skip_networking"><code class="literal">skip_networking</code></a>
          system variable enabled, it will not accept TCP/IP connections
          at all. If the server was started with the
          <a class="link" href="server-administration.html#sysvar_bind_address"><code class="literal">bind_address</code></a> system variable
          set to <code class="literal">127.0.0.1</code>, it will listen for TCP/IP
          connections only locally on the loopback interface and will
          not accept remote connections.
        </p><p>
          Check to make sure that there is no firewall blocking access
          to MySQL. Your firewall may be configured on the basis of the
          application being executed, or the port number used by MySQL
          for communication (3306 by default). Under Linux or Unix,
          check your IP tables (or similar) configuration to ensure that
          the port has not been blocked. Under Windows, applications
          such as ZoneAlarm or Windows Firewall may need to be
          configured not to block the MySQL port.
        </p><p>
          Here are some reasons the <code class="literal">Can't connect to local
          MySQL server</code> error might occur:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> is not running on the local
              host. Check your operating system's process list to ensure
              the <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> process is present.
            </p></li><li class="listitem"><p>
              You're running a MySQL server on Windows with many TCP/IP
              connections to it. If you're experiencing that quite often
              your clients get that error, you can find a workaround
              here:
              <a class="xref" href="error-handling.html#can-not-connect-to-server-on-windows" title="B.4.2.2.2 Connection to MySQL Server Failing on Windows">Section B.4.2.2.2, “Connection to MySQL Server Failing on Windows”</a>.
            </p></li><li class="listitem"><p>
              Someone has removed the Unix socket file that
              <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> uses
              (<code class="filename">/tmp/mysql.sock</code> by default). For
              example, you might have a <span class="command"><strong>cron</strong></span> job that
              removes old files from the <code class="filename">/tmp</code>
              directory. You can always run <a class="link" href="programs.html#mysqladmin" title="4.5.2 mysqladmin — Client for Administering a MySQL Server"><span class="command"><strong>mysqladmin
              version</strong></span></a> to check whether the Unix socket file
              that <a class="link" href="programs.html#mysqladmin" title="4.5.2 mysqladmin — Client for Administering a MySQL Server"><span class="command"><strong>mysqladmin</strong></span></a> is trying to use really
              exists. The fix in this case is to change the
              <span class="command"><strong>cron</strong></span> job to not remove
              <code class="filename">mysql.sock</code> or to place the socket
              file somewhere else. See
              <a class="xref" href="error-handling.html#problems-with-mysql-sock" title="B.4.3.6 How to Protect or Change the MySQL Unix Socket File">Section B.4.3.6, “How to Protect or Change the MySQL Unix Socket File”</a>.
            </p></li><li class="listitem"><p>
              You have started the <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> server with
              the
              <a class="link" href="server-administration.html#option_mysqld_socket"><code class="option">--socket=/path/to/socket</code></a>
              option, but forgotten to tell client programs the new name
              of the socket file. If you change the socket path name for
              the server, you must also notify the MySQL clients. You
              can do this by providing the same
              <a class="link" href="programs.html#option_general_socket"><code class="option">--socket</code></a> option when you
              run client programs. You also need to ensure that clients
              have permission to access the
              <code class="filename">mysql.sock</code> file. To find out where
              the socket file is, you can do:
            </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>netstat -ln | grep mysql</code></strong>
</pre><p>
              See <a class="xref" href="error-handling.html#problems-with-mysql-sock" title="B.4.3.6 How to Protect or Change the MySQL Unix Socket File">Section B.4.3.6, “How to Protect or Change the MySQL Unix Socket File”</a>.
            </p></li><li class="listitem"><p>
              You are using Linux and one server thread has died (dumped
              core). In this case, you must kill the other
              <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> threads (for example, with
              <a class="link" href="sql-statements.html#kill" title="13.7.6.4 KILL Statement"><span class="command"><strong>kill</strong></span></a>) before you can restart the MySQL
              server. See <a class="xref" href="error-handling.html#crashing" title="B.4.3.3 What to Do If MySQL Keeps Crashing">Section B.4.3.3, “What to Do If MySQL Keeps Crashing”</a>.
            </p></li><li class="listitem"><p>
              The server or client program might not have the proper
              access privileges for the directory that holds the Unix
              socket file or the socket file itself. In this case, you
              must either change the access privileges for the directory
              or socket file so that the server and clients can access
              them, or restart <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> with a
              <a class="link" href="server-administration.html#option_mysqld_socket"><code class="option">--socket</code></a> option that
              specifies a socket file name in a directory where the
              server can create it and where client programs can access
              it.
</p></li></ul>
</div>
<p>
          If you get the error message <code class="literal">Can't connect to MySQL
          server on some_host</code>, you can try the following
          things to find out what the problem is:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              Check whether the server is running on that host by
              executing <code class="literal">telnet some_host 3306</code> and
              pressing the Enter key a couple of times. (3306 is the
              default MySQL port number. Change the value if your server
              is listening to a different port.) If there is a MySQL
              server running and listening to the port, you should get a
              response that includes the server's version number. If you
              get an error such as <code class="literal">telnet: Unable to connect to
              remote host: Connection refused</code>, then there is
              no server running on the given port.
            </p></li><li class="listitem"><p>
              If the server is running on the local host, try using
              <a class="link" href="programs.html#mysqladmin" title="4.5.2 mysqladmin — Client for Administering a MySQL Server"><span class="command"><strong>mysqladmin -h localhost variables</strong></span></a> to
              connect using the Unix socket file. Verify the TCP/IP port
              number that the server is configured to listen to (it is
              the value of the <a class="link" href="server-administration.html#sysvar_port"><code class="literal">port</code></a>
              variable.)
            </p></li><li class="listitem"><p>
              If you are running under Linux and Security-Enhanced Linux
              (SELinux) is enabled, see
              <a class="xref" href="error-handling.html#howto-set-selinux-contexts" title="B.4.2.2.1 Set SELinux context for MySQL Server">Section B.4.2.2.1, “Set SELinux context for MySQL Server”</a>.
</p></li></ul>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h5 class="title"><a name="howto-set-selinux-contexts"></a>B.4.2.2.1 Set SELinux context for MySQL Server</h5>

</div>

</div>

</div>
<p>
            The MySQL server reads from and writes to many files, and if
            the SELinux context is not set correctly on these files then
            the mysqld process could block access to MySQL files. In
            some cases, this could stop mysqld from logging errors.
</p>
<div class="simplesect">

<div class="titlepage">
<div>

<div class="simple">
<h6 class="title"><a name="howto-set-selinux-contexts-tool-install"></a>Required Tools</h6>
</div>

</div>

</div>
<p>
              The semanage binary is used in this guide to manage
              context; on Enterprise Linux it's part of the
              <code class="literal">policycoreutils-python</code> package:
</p><pre data-lang="terminal" class="programlisting">shell&gt; yum install policycoreutils-python</pre>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">

<div class="admon-title">
Note
</div>
<p>
                RHEL 6 with Python 2.6: to use semanage with early
                versions of RHEL 6 with python 2.6, you may need to
                install a backport of the OrderedDict python collection
                module using python-pip from the EPEL repository.
</p>
</div>

</div>
<div class="simplesect">
<div class="titlepage">
<div>
<div class="simple">
<h6 class="title"><a name="howto-set-selinux-contexts-list"></a>List Current MySQL Context</h6>
</div>

</div>

</div>
<p>
              List them using the following:
</p><pre data-lang="terminal" class="programlisting">shell&gt; semanage fcontext -l | grep -i mysql</pre>
</div>
<div class="simplesect">
<div class="titlepage">
<div>
<div class="simple">
<h6 class="title"><a name="howto-set-selinux-contexts-set-data-dir"></a>Set MySQL Data Directory Context</h6>
</div>

</div>

</div>
<p>
              The default data directory location is
              <code class="filename">/var/lib/mysql/</code>; and the SELinux
              context used is <code class="literal">mysqld_db_t</code>.
            </p><p>
              If you edit the configuration file to use a different
              location for the data directory, or for any of the files
              normally in the data directory (such as the binary logs)
              you may need to set the context for the new location. For
              example:
            </p><pre data-lang="terminal" class="programlisting">shell&gt; semanage fcontext -a -t mysqld_db_t "/path/to/my/custom/datadir(/.*)?"
shell&gt; restorecon -Rv /path/to/my/custom/datadir

shell&gt; semanage fcontext -a -t mysqld_db_t "/path/to/my/custom/logdir(/.*)?"
shell&gt; restorecon -Rv /path/to/my/custom/logdir</pre>
</div>
<div class="simplesect">
<div class="titlepage">
<div>
<div class="simple">
<h6 class="title"><a name="howto-set-selinux-contexts-set-error-log"></a>Set MySQL Error Log File Context</h6>
</div>

</div>

</div>
<p>
              The default location for RedHat RPMs is
              <code class="filename">/var/log/mysqld.log</code>; and the SELinux
              context used is <code class="literal">mysqld_log_t</code>.
            </p><p>
              If you edit the configuration file to use a different
              location then you may need to set the context for the new
              location. For example:
            </p><pre data-lang="terminal" class="programlisting">shell&gt; semanage fcontext -a -t mysqld_log_t "/path/to/my/custom/error.log"
shell&gt; restorecon -Rv /path/to/my/custom/error.log</pre>
</div>
<div class="simplesect">
<div class="titlepage">
<div>
<div class="simple">
<h6 class="title"><a name="howto-set-selinux-contexts-set-pid-file"></a>Set PID File Context</h6>
</div>

</div>

</div>
<p>
              The default location for the PID file is
              <code class="filename">/var/run/mysqld/mysqld.pid</code>; and the
              SELinux context used is
              <code class="literal">mysqld_var_run_t</code>.
            </p><p>
              If you edit the configuration file to use a different
              location then you may need to set the context for the new
              location. For example:
            </p><pre data-lang="terminal" class="programlisting">shell&gt; semanage fcontext -a -t mysqld_var_run_t "/path/to/my/custom/pidfile/directory/.*?"
shell&gt; restorecon -Rv /path/to/my/custom/pidfile/directory
</pre>
</div>
<div class="simplesect">
<div class="titlepage">
<div>
<div class="simple">
<h6 class="title"><a name="howto-set-selinux-contexts-set-unix-domain-socket"></a>Set unix-domain Socket Context</h6>
</div>

</div>

</div>
<p>
              The default location for the unix-domain socket is
              <code class="filename">/var/lib/mysql/mysql.sock</code>; and the
              SELinux context used is
              <code class="literal">mysqld_var_run_t</code>.
            </p><p>
              If you edit the configuration file to use a different
              location then you may need to set the context for the new
              location. For example:
            </p><pre data-lang="terminal" class="programlisting">shell&gt; semanage fcontext -a -t mysqld_var_run_t "/path/to/my/custom/mysql\.sock"
shell&gt; restorecon -Rv /path/to/my/custom/mysql.sock</pre>
</div>
<div class="simplesect">
<div class="titlepage">
<div>
<div class="simple">
<h6 class="title"><a name="howto-set-selinux-contexts-set-tcp-port"></a>Set TCP Port Context</h6>
</div>

</div>

</div>
<p>
              The default TCP port is <code class="literal">3306</code>; and the
              SELinux context used is <code class="literal">mysqld_port_t</code>.
            </p><p>
              If you configure mysqld to use a different TCP
              <a class="link" href="server-administration.html#sysvar_port"><code class="literal">port</code></a>, or you enable
              features like Group Replication which use additional ports
              such as 33061 (configured by
              <a class="link" href="group-replication.html#sysvar_group_replication_local_address"><code class="literal">group_replication_local_address</code></a>),
              you might need to set the context for the new port. If the
              port is not configured correctly in SELinux, MySQL
              features might not function correctly. For example to open
              port 33061:
            </p><pre data-lang="terminal" class="programlisting">shell&gt; semanage port -a -t mysqld_port_t -p tcp 33061
shell&gt; restorecon</pre>
</div>
<div class="simplesect">
<div class="titlepage">
<div>
<div class="simple">
<h6 class="title"><a name="howto-set-selinux-contexts-set-secure-file-priv"></a>Set secure_file_priv Directory Context</h6>
</div>

</div>

</div>
<p>
              For MySQL versions since 5.5.53, 5.6.34, 5.7.16, and
              8.0.11.
            </p><p>
              Installing the MySQL server RPM creates a
              <code class="filename">/var/lib/mysql-files/</code> directory, but
              does not set the SELinux context on this directory. This
              directory is intended to be used for operations such as
              <code class="literal">SELECT ... INTO OUTFILE</code>.
            </p><p>
              If you enabled the use of this directory by setting
              <code class="literal">secure_file_priv</code>, you may need to set
              the context like so:
            </p><pre data-lang="terminal" class="programlisting">shell&gt; semanage fcontext -a -t mysqld_db_t "/var/lib/mysql-files/(/.*)?"
shell&gt; restorecon -Rv /var/lib/mysql-files</pre><p>
              Edit this path if you used a different location. For
              security purposes, this directory should never be within
              the data directory.
            </p><p>
              For more information about this variable, see the
              <a class="link" href="server-administration.html#sysvar_secure_file_priv"><code class="literal">secure_file_priv</code></a>
              documentation.
</p>
</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h5 class="title"><a name="can-not-connect-to-server-on-windows"></a>B.4.2.2.2 Connection to MySQL Server Failing on Windows</h5>

</div>

</div>

</div>
<p>
            When you're running a MySQL server on Windows with many
            TCP/IP connections to it, and you're experiencing that quite
            often your clients get a <code class="literal">Can't connect to MySQL
            server</code> error, the reason might be that Windows
            does not allow for enough ephemeral (short-lived) ports to
            serve those connections.
          </p><p>
            The purpose of <code class="literal">TIME_WAIT</code> is to keep a
            connection accepting packets even after the connection has
            been closed. This is because Internet routing can cause a
            packet to take a slow route to its destination and it may
            arrive after both sides have agreed to close. If the port is
            in use for a new connection, that packet from the old
            connection could break the protocol or compromise personal
            information from the original connection. The
            <code class="literal">TIME_WAIT</code> delay prevents this by ensuring
            that the port cannot be reused until after some time has
            been permitted for those delayed packets to arrive.
          </p><p>
            It is safe to reduce <code class="literal">TIME_WAIT</code> greatly on
            LAN connections because there is little chance of packets
            arriving at very long delays, as they could through the
            Internet with its comparatively large distances and
            latencies.
          </p><p>
            Windows permits ephemeral (short-lived) TCP ports to the
            user. After any port is closed it will remain in a
            <code class="literal">TIME_WAIT</code> status for 120 seconds. The
            port will not be available again until this time expires.
            The default range of port numbers depends on the version of
            Windows, with a more limited number of ports in older
            versions:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
                Windows through Server 2003: Ports in range
                1025–5000
              </p></li><li class="listitem"><p>
                Windows Vista, Server 2008, and newer: Ports in range
                49152–65535
</p></li></ul>
</div>
<p>
            With a small stack of available TCP ports (5000) and a high
            number of TCP ports being open and closed over a short
            period of time along with the <code class="literal">TIME_WAIT</code>
            status you have a good chance for running out of ports.
            There are two ways to address this problem:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
                Reduce the number of TCP ports consumed quickly by
                investigating connection pooling or persistent
                connections where possible
              </p></li><li class="listitem"><p>
                Tune some settings in the Windows registry (see below)
</p></li></ul>
</div>
<div class="important" style="margin-left: 0.5in; margin-right: 0.5in;">
<div class="admon-title">
Important
</div>
<p>
              The following procedure involves modifying the Windows
              registry. Before you modify the registry, make sure to
              back it up and make sure that you understand how to
              restore it if a problem occurs. For information about how
              to back up, restore, and edit the registry, view the
              following article in the Microsoft Knowledge Base:
              <a class="ulink" href="http://support.microsoft.com/kb/256986/EN-US/" target="_top">http://support.microsoft.com/kb/256986/EN-US/</a>.
</p>
</div>
<div class="orderedlist">
<ol class="orderedlist" type="1"><li class="listitem"><p>
                Start Registry Editor
                (<code class="filename">Regedt32.exe</code>).
              </p></li><li class="listitem"><p>
                Locate the following key in the registry:
              </p><pre data-lang="none" class="programlisting">HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters</pre></li><li class="listitem"><p>
                On the <code class="literal">Edit</code> menu, click <code class="literal">Add
                Value</code>, and then add the following registry
                value:
              </p><pre data-lang="none" class="programlisting">Value Name: MaxUserPort
Data Type: REG_DWORD
Value: 65534</pre><p>
                This sets the number of ephemeral ports available to any
                user. The valid range is between 5000 and 65534
                (decimal). The default value is 0x1388 (5000 decimal).
              </p></li><li class="listitem"><p>
                On the <code class="literal">Edit</code> menu, click <code class="literal">Add
                Value</code>, and then add the following registry
                value:
              </p><pre data-lang="none" class="programlisting">Value Name: TcpTimedWaitDelay
Data Type: REG_DWORD
Value: 30</pre><p>
                This sets the number of seconds to hold a TCP port
                connection in <code class="literal">TIME_WAIT</code> state before
                closing. The valid range is between 30 and 300 decimal,
                although you may wish to check with Microsoft for the
                latest permitted values. The default value is 0x78 (120
                decimal).
              </p></li><li class="listitem"><p>
                Quit Registry Editor.
              </p></li><li class="listitem"><p>
                Reboot the machine.
</p></li></ol>
</div>
<p>
            Note: Undoing the above should be as simple as deleting the
            registry entries you've created.
</p>
</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="error-lost-connection"></a>B.4.2.3 Lost connection to MySQL server</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734184092784"></a><a class="indexterm" name="idm46734184091328"></a><a class="indexterm" name="idm46734184089840"></a><p>
          There are three likely causes for this error message.
        </p><p>
          Usually it indicates network connectivity trouble and you
          should check the condition of your network if this error
          occurs frequently. If the error message includes <span class="quote">“<span class="quote">during
          query,</span>”</span> this is probably the case you are experiencing.
        </p><p>
          Sometimes the <span class="quote">“<span class="quote">during query</span>”</span> form happens when
          millions of rows are being sent as part of one or more
          queries. If you know that this is happening, you should try
          increasing <a class="link" href="server-administration.html#sysvar_net_read_timeout"><code class="literal">net_read_timeout</code></a>
          from its default of 30 seconds to 60 seconds or longer,
          sufficient for the data transfer to complete.
        </p><p>
          More rarely, it can happen when the client is attempting the
          initial connection to the server. In this case, if your
          <a class="link" href="server-administration.html#sysvar_connect_timeout"><code class="literal">connect_timeout</code></a> value is set
          to only a few seconds, you may be able to resolve the problem
          by increasing it to ten seconds, perhaps more if you have a
          very long distance or slow connection. You can determine
          whether you are experiencing this more uncommon cause by using
          <code class="literal">SHOW GLOBAL STATUS LIKE 'Aborted_connects'</code>.
          It will increase by one for each initial connection attempt
          that the server aborts. You may see <span class="quote">“<span class="quote">reading
          authorization packet</span>”</span> as part of the error message; if
          so, that also suggests that this is the solution that you
          need.
        </p><p>
          If the cause is none of those just described, you may be
          experiencing a problem with
          <a class="link" href="data-types.html#blob" title="11.3.4 The BLOB and TEXT Types"><code class="literal">BLOB</code></a> values that are larger
          than <a class="link" href="server-administration.html#sysvar_max_allowed_packet"><code class="literal">max_allowed_packet</code></a>,
          which can cause this error with some clients. Sometime you may
          see an <a class="link" href="error-handling.html#error_er_net_packet_too_large"><code class="literal">ER_NET_PACKET_TOO_LARGE</code></a>
          error, and that confirms that you need to increase
          <a class="link" href="server-administration.html#sysvar_max_allowed_packet"><code class="literal">max_allowed_packet</code></a>.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="password-too-long"></a>B.4.2.4 Password Fails When Entered Interactively</h4>

</div>

</div>

</div>
<p>
          MySQL client programs prompt for a password when invoked with
          a <a class="link" href="programs.html#option_general_password"><code class="option">--password</code></a> or
          <code class="option">-p</code> option that has no following password
          value:
        </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>mysql -u <em class="replaceable"><code>user_name</code></em> -p</code></strong>
Enter password:
</pre><p>
          On some systems, you may find that your password works when
          specified in an option file or on the command line, but not
          when you enter it interactively at the <code class="literal">Enter
          password:</code> prompt. This occurs when the library
          provided by the system to read passwords limits password
          values to a small number of characters (typically eight). That
          is a problem with the system library, not with MySQL. To work
          around it, change your MySQL password to a value that is eight
          or fewer characters long, or put your password in an option
          file.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="blocked-host"></a>B.4.2.5 Host 'host_name' is blocked</h4>

</div>

</div>

</div>
<p>
          If the following error occurs, it means that
          <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> has received many connection
          requests from the given host that were interrupted in the
          middle:
        </p><pre data-lang="none" class="programlisting">Host '<em class="replaceable"><code>host_name</code></em>' is blocked because of many connection errors.
Unblock with 'mysqladmin flush-hosts'
</pre><p>
          The value of the
          <a class="link" href="server-administration.html#sysvar_max_connect_errors"><code class="literal">max_connect_errors</code></a> system
          variable determines how many successive interrupted connection
          requests are permitted. After
          <a class="link" href="server-administration.html#sysvar_max_connect_errors"><code class="literal">max_connect_errors</code></a> failed
          requests without a successful connection,
          <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> assumes that something is wrong (for
          example, that someone is trying to break in), and blocks the
          host from further connections until you flush the host cache
          by executing a <a class="link" href="sql-statements.html#flush-hosts"><code class="literal">FLUSH HOSTS</code></a>
          statement, a <a class="link" href="sql-statements.html#truncate-table" title="13.1.34 TRUNCATE TABLE Statement"><code class="literal">TRUNCATE TABLE</code></a>
          statement that truncates the Performance Schema
          <a class="link" href="performance-schema.html#host-cache-table" title="25.12.16.1 The host_cache Table"><code class="literal">host_cache</code></a> table, or a
          <a class="link" href="programs.html#mysqladmin" title="4.5.2 mysqladmin — Client for Administering a MySQL Server"><span class="command"><strong>mysqladmin flush-hosts</strong></span></a> command.
        </p><p>
          To adjust the permitted number of successive connection
          errors, set
          <a class="link" href="server-administration.html#sysvar_max_connect_errors"><code class="literal">max_connect_errors</code></a> at server
          startup. For example, put these lines in the server
          <code class="filename">my.cnf</code> file:
        </p><pre data-lang="ini" class="programlisting">[mysqld]
max_connect_errors=10000</pre><p>
          The value can also be set at runtime:
        </p><pre data-lang="sql" class="programlisting">SET GLOBAL max_connect_errors=10000;</pre><p>
          If you get the <code class="literal">Host
          '<em class="replaceable"><code>host_name</code></em>' is blocked</code>
          error message for a given host, you should first verify that
          there is nothing wrong with TCP/IP connections from that host.
          If you are having network problems, it does no good to
          increase the value of
          <a class="link" href="server-administration.html#sysvar_max_connect_errors"><code class="literal">max_connect_errors</code></a>.
        </p><p>
          For more information about how the host cache works, see
          <a class="xref" href="server-administration.html#host-cache" title="5.1.11.2 DNS Lookups and the Host Cache">Section 5.1.11.2, “DNS Lookups and the Host Cache”</a>.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="too-many-connections"></a>B.4.2.6 Too many connections</h4>

</div>

</div>

</div>
<p>
          If clients encounter <code class="literal">Too many connections</code>
          errors when attempting to connect to the
          <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> server, all available connections
          are in use by other clients.
        </p><p>
          The permitted number of connections is controlled by the
          <a class="link" href="server-administration.html#sysvar_max_connections"><code class="literal">max_connections</code></a> system
          variable. The default value is 151 to improve performance when
          MySQL is used with the Apache Web server. To support more
          connections, set
          <a class="link" href="server-administration.html#sysvar_max_connections"><code class="literal">max_connections</code></a> to a larger
          value.
        </p><p>
          <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> actually permits
          <a class="link" href="server-administration.html#sysvar_max_connections"><code class="literal">max_connections</code></a>
          + 1 client connections. The extra connection is reserved for
          use by accounts that have the
          <a class="link" href="security.html#priv_super"><code class="literal">SUPER</code></a> privilege. By granting
          the privilege to administrators and not to normal users (who
          should not need it), an administrator who also has the
          <a class="link" href="security.html#priv_process"><code class="literal">PROCESS</code></a> privilege can connect
          to the server and use <a class="link" href="sql-statements.html#show-processlist" title="13.7.5.29 SHOW PROCESSLIST Statement"><code class="literal">SHOW
          PROCESSLIST</code></a> to diagnose problems even if the maximum
          number of unprivileged clients are connected. See
          <a class="xref" href="sql-statements.html#show-processlist" title="13.7.5.29 SHOW PROCESSLIST Statement">Section 13.7.5.29, “SHOW PROCESSLIST Statement”</a>.
        </p><p>
          For more information about how the server handles client
          connections, see <a class="xref" href="server-administration.html#connection-interfaces" title="5.1.11.1 Connection Interfaces">Section 5.1.11.1, “Connection Interfaces”</a>.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="out-of-memory"></a>B.4.2.7 Out of memory</h4>

</div>

</div>

</div>
<p>
          If you issue a query using the <a class="link" href="programs.html#mysql" title="4.5.1 mysql — The MySQL Command-Line Client"><span class="command"><strong>mysql</strong></span></a> client
          program and receive an error like the following one, it means
          that <a class="link" href="programs.html#mysql" title="4.5.1 mysql — The MySQL Command-Line Client"><span class="command"><strong>mysql</strong></span></a> does not have enough memory to
          store the entire query result:
        </p><pre data-lang="none" class="programlisting">mysql: Out of memory at line 42, 'malloc.c'
mysql: needed 8136 byte (8k), memory in use: 12481367 bytes (12189k)
ERROR 2008: MySQL client ran out of memory</pre><p>
          To remedy the problem, first check whether your query is
          correct. Is it reasonable that it should return so many rows?
          If not, correct the query and try again. Otherwise, you can
          invoke <a class="link" href="programs.html#mysql" title="4.5.1 mysql — The MySQL Command-Line Client"><span class="command"><strong>mysql</strong></span></a> with the
          <a class="link" href="programs.html#option_mysql_quick"><code class="option">--quick</code></a> option. This causes it
          to use the <a class="link" href="connectors-apis.html#mysql-use-result" title="27.7.6.77 mysql_use_result()"><code class="literal">mysql_use_result()</code></a>
          C API function to retrieve the result set, which places less
          of a load on the client (but more on the server).
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="gone-away"></a>B.4.2.8 MySQL server has gone away</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734184018912"></a><a class="indexterm" name="idm46734184017872"></a><p>
          This section also covers the related <code class="literal">Lost connection
          to server during query</code> error.
        </p><p>
          The most common reason for the <code class="literal">MySQL server has gone
          away</code> error is that the server timed out and closed
          the connection. In this case, you normally get one of the
          following error codes (which one you get is operating
          system-dependent).
</p>
<div class="informaltable">
<table summary="MySQL server has gone away error codes and a description of each code."><col width="35%"><col width="65%"><thead><tr>
              <th scope="col">Error Code</th>
              <th scope="col">Description</th>
            </tr></thead><tbody><tr>
              <td scope="row"><a class="link" href="error-handling.html#error_cr_server_gone_error"><code class="literal">CR_SERVER_GONE_ERROR</code></a></td>
              <td>The client couldn't send a question to the server.</td>
            </tr><tr>
              <td scope="row"><a class="link" href="error-handling.html#error_cr_server_lost"><code class="literal">CR_SERVER_LOST</code></a></td>
              <td>The client didn't get an error when writing to the server, but it didn't
                get a full answer (or any answer) to the question.</td>
</tr></tbody></table>
</div>
<p>
          By default, the server closes the connection after eight hours
          if nothing has happened. You can change the time limit by
          setting the <a class="link" href="server-administration.html#sysvar_wait_timeout"><code class="literal">wait_timeout</code></a>
          variable when you start <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>. See
          <a class="xref" href="server-administration.html#server-system-variables" title="5.1.7 Server System Variables">Section 5.1.7, “Server System Variables”</a>.
        </p><p>
          If you have a script, you just have to issue the query again
          for the client to do an automatic reconnection. This assumes
          that you have automatic reconnection in the client enabled
          (which is the default for the <code class="literal">mysql</code>
          command-line client).
        </p><p>
          Some other common reasons for the <code class="literal">MySQL server has
          gone away</code> error are:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              You (or the db administrator) has killed the running
              thread with a <a class="link" href="sql-statements.html#kill" title="13.7.6.4 KILL Statement"><code class="literal">KILL</code></a>
              statement or a <a class="link" href="programs.html#mysqladmin" title="4.5.2 mysqladmin — Client for Administering a MySQL Server"><span class="command"><strong>mysqladmin kill</strong></span></a> command.
            </p></li><li class="listitem"><p>
              You tried to run a query after closing the connection to
              the server. This indicates a logic error in the
              application that should be corrected.
            </p></li><li class="listitem"><p>
              A client application running on a different host does not
              have the necessary privileges to connect to the MySQL
              server from that host.
            </p></li><li class="listitem"><p>
              You got a timeout from the TCP/IP connection on the client
              side. This may happen if you have been using the commands:
              <a class="link" href="connectors-apis.html#mysql-options" title="27.7.6.50 mysql_options()"><code class="literal">mysql_options(...,
              MYSQL_OPT_READ_TIMEOUT,...)</code></a> or
              <a class="link" href="connectors-apis.html#mysql-options" title="27.7.6.50 mysql_options()"><code class="literal">mysql_options(...,
              MYSQL_OPT_WRITE_TIMEOUT,...)</code></a>. In this case
              increasing the timeout may help solve the problem.
            </p></li><li class="listitem"><p>
              You have encountered a timeout on the server side and the
              automatic reconnection in the client is disabled (the
              <code class="literal">reconnect</code> flag in the
              <code class="literal">MYSQL</code> structure is equal to 0).
            </p></li><li class="listitem"><p>
              You are using a Windows client and the server had dropped
              the connection (probably because
              <a class="link" href="server-administration.html#sysvar_wait_timeout"><code class="literal">wait_timeout</code></a> expired)
              before the command was issued.
            </p><p>
              The problem on Windows is that in some cases MySQL does
              not get an error from the OS when writing to the TCP/IP
              connection to the server, but instead gets the error when
              trying to read the answer from the connection.
            </p><p>
              The solution to this is to either do a
              <a class="link" href="connectors-apis.html#mysql-ping" title="27.7.6.52 mysql_ping()"><code class="literal">mysql_ping()</code></a> on the
              connection if there has been a long time since the last
              query (this is what Connector/ODBC does) or set
              <a class="link" href="server-administration.html#sysvar_wait_timeout"><code class="literal">wait_timeout</code></a> on the
              <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> server so high that it in
              practice never times out.
            </p></li><li class="listitem"><p>
              You can also get these errors if you send a query to the
              server that is incorrect or too large. If
              <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> receives a packet that is too
              large or out of order, it assumes that something has gone
              wrong with the client and closes the connection. If you
              need big queries (for example, if you are working with big
              <a class="link" href="data-types.html#blob" title="11.3.4 The BLOB and TEXT Types"><code class="literal">BLOB</code></a> columns), you can
              increase the query limit by setting the server's
              <a class="link" href="server-administration.html#sysvar_max_allowed_packet"><code class="literal">max_allowed_packet</code></a>
              variable, which has a default value of 4MB. You may also
              need to increase the maximum packet size on the client
              end. More information on setting the packet size is given
              in <a class="xref" href="error-handling.html#packet-too-large" title="B.4.2.9 Packet Too Large">Section B.4.2.9, “Packet Too Large”</a>.
            </p><p>
              An <a class="link" href="sql-statements.html#insert" title="13.2.5 INSERT Statement"><code class="literal">INSERT</code></a> or
              <a class="link" href="sql-statements.html#replace" title="13.2.8 REPLACE Statement"><code class="literal">REPLACE</code></a> statement that
              inserts a great many rows can also cause these sorts of
              errors. Either one of these statements sends a single
              request to the server irrespective of the number of rows
              to be inserted; thus, you can often avoid the error by
              reducing the number of rows sent per
              <a class="link" href="sql-statements.html#insert" title="13.2.5 INSERT Statement"><code class="literal">INSERT</code></a> or
              <a class="link" href="sql-statements.html#replace" title="13.2.8 REPLACE Statement"><code class="literal">REPLACE</code></a>.
            </p></li><li class="listitem"><p>
              It is also possible to see this error if host name lookups
              fail (for example, if the DNS server on which your server
              or network relies goes down). This is because MySQL is
              dependent on the host system for name resolution, but has
              no way of knowing whether it is working—from MySQL's
              point of view the problem is indistinguishable from any
              other network timeout.
            </p><p>
              You may also see the <code class="literal">MySQL server has gone
              away</code> error if MySQL is started with the
              <a class="link" href="server-administration.html#sysvar_skip_networking"><code class="literal">skip_networking</code></a> system
              variable enabled.
            </p><p>
              Another networking issue that can cause this error occurs
              if the MySQL port (default 3306) is blocked by your
              firewall, thus preventing any connections at all to the
              MySQL server.
            </p></li><li class="listitem"><p>
              You can also encounter this error with applications that
              fork child processes, all of which try to use the same
              connection to the MySQL server. This can be avoided by
              using a separate connection for each child process.
            </p></li><li class="listitem"><p>
              You have encountered a bug where the server died while
              executing the query.
</p></li></ul>
</div>
<p>
          You can check whether the MySQL server died and restarted by
          executing <a class="link" href="programs.html#mysqladmin" title="4.5.2 mysqladmin — Client for Administering a MySQL Server"><span class="command"><strong>mysqladmin version</strong></span></a> and examining
          the server's uptime. If the client connection was broken
          because <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> crashed and restarted, you
          should concentrate on finding the reason for the crash. Start
          by checking whether issuing the query again kills the server
          again. See <a class="xref" href="error-handling.html#crashing" title="B.4.3.3 What to Do If MySQL Keeps Crashing">Section B.4.3.3, “What to Do If MySQL Keeps Crashing”</a>.
        </p><p>
          You can obtain more information about lost connections by
          starting <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> with the
          <a class="link" href="server-administration.html#sysvar_log_error_verbosity"><code class="literal">log_error_verbosity</code></a> system
          variable set to 3. This logs some of the disconnection
          messages in the <code class="literal">hostname.err</code> file. See
          <a class="xref" href="server-administration.html#error-log" title="5.4.2 The Error Log">Section 5.4.2, “The Error Log”</a>.
        </p><p>
          If you want to create a bug report regarding this problem, be
          sure that you include the following information:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              Indicate whether the MySQL server died. You can find
              information about this in the server error log. See
              <a class="xref" href="error-handling.html#crashing" title="B.4.3.3 What to Do If MySQL Keeps Crashing">Section B.4.3.3, “What to Do If MySQL Keeps Crashing”</a>.
            </p></li><li class="listitem"><p>
              If a specific query kills <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> and
              the tables involved were checked with
              <a class="link" href="sql-statements.html#check-table" title="13.7.2.2 CHECK TABLE Statement"><code class="literal">CHECK TABLE</code></a> before you ran
              the query, can you provide a reproducible test case? See
              <a class="xref" href="extending-mysql.html#porting" title="28.5 Debugging and Porting MySQL">Section 28.5, “Debugging and Porting MySQL”</a>.
            </p></li><li class="listitem"><p>
              What is the value of the
              <a class="link" href="server-administration.html#sysvar_wait_timeout"><code class="literal">wait_timeout</code></a> system
              variable in the MySQL server? (<a class="link" href="programs.html#mysqladmin" title="4.5.2 mysqladmin — Client for Administering a MySQL Server"><span class="command"><strong>mysqladmin
              variables</strong></span></a> gives you the value of this variable.)
            </p></li><li class="listitem"><p>
              Have you tried to run <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> with the
              general query log enabled to determine whether the problem
              query appears in the log? (See
              <a class="xref" href="server-administration.html#query-log" title="5.4.3 The General Query Log">Section 5.4.3, “The General Query Log”</a>.)
</p></li></ul>
</div>
<p>
          See also <a class="xref" href="error-handling.html#communication-errors" title="B.4.2.10 Communication Errors and Aborted Connections">Section B.4.2.10, “Communication Errors and Aborted Connections”</a>, and
          <a class="xref" href="introduction.html#bug-reports" title="1.7 How to Report Bugs or Problems">Section 1.7, “How to Report Bugs or Problems”</a>.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="packet-too-large"></a>B.4.2.9 Packet Too Large</h4>

</div>

</div>

</div>
<p>
          A communication packet is a single SQL statement sent to the
          MySQL server, a single row that is sent to the client, or a
          binary log event sent from a master replication server to a
          slave.
        </p><p>
          The largest possible packet that can be transmitted to or from
          a MySQL 5.7 server or client is 1GB.
        </p><p>
          When a MySQL client or the <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> server
          receives a packet bigger than
          <a class="link" href="server-administration.html#sysvar_max_allowed_packet"><code class="literal">max_allowed_packet</code></a> bytes, it
          issues an
          <a class="link" href="error-handling.html#error_er_net_packet_too_large"><code class="literal">ER_NET_PACKET_TOO_LARGE</code></a> error
          and closes the connection. With some clients, you may also get
          a <code class="literal">Lost connection to MySQL server during
          query</code> error if the communication packet is too
          large.
        </p><p>
          Both the client and the server have their own
          <a class="link" href="server-administration.html#sysvar_max_allowed_packet"><code class="literal">max_allowed_packet</code></a> variable,
          so if you want to handle big packets, you must increase this
          variable both in the client and in the server.
        </p><p>
          If you are using the <a class="link" href="programs.html#mysql" title="4.5.1 mysql — The MySQL Command-Line Client"><span class="command"><strong>mysql</strong></span></a> client program,
          its default
          <a class="link" href="server-administration.html#sysvar_max_allowed_packet"><code class="literal">max_allowed_packet</code></a> variable
          is 16MB. To set a larger value, start <a class="link" href="programs.html#mysql" title="4.5.1 mysql — The MySQL Command-Line Client"><span class="command"><strong>mysql</strong></span></a>
          like this:
        </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>mysql --max_allowed_packet=32M</code></strong>
</pre><p>
          That sets the packet size to 32MB.
        </p><p>
          The server's default
          <a class="link" href="server-administration.html#sysvar_max_allowed_packet"><code class="literal">max_allowed_packet</code></a> value is
          4MB. You can increase this if the server needs to handle big
          queries (for example, if you are working with big
          <a class="link" href="data-types.html#blob" title="11.3.4 The BLOB and TEXT Types"><code class="literal">BLOB</code></a> columns). For example, to
          set the variable to 16MB, start the server like this:
        </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>mysqld --max_allowed_packet=16M</code></strong>
</pre><p>
          You can also use an option file to set
          <a class="link" href="server-administration.html#sysvar_max_allowed_packet"><code class="literal">max_allowed_packet</code></a>. For
          example, to set the size for the server to 16MB, add the
          following lines in an option file:
        </p><pre data-lang="ini" class="programlisting">[mysqld]
max_allowed_packet=16M</pre><p>
          It is safe to increase the value of this variable because the
          extra memory is allocated only when needed. For example,
          <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> allocates more memory only when you
          issue a long query or when <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> must
          return a large result row. The small default value of the
          variable is a precaution to catch incorrect packets between
          the client and server and also to ensure that you do not run
          out of memory by using large packets accidentally.
        </p><p>
          You can also get strange problems with large packets if you
          are using large <a class="link" href="data-types.html#blob" title="11.3.4 The BLOB and TEXT Types"><code class="literal">BLOB</code></a> values but
          have not given <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> access to enough
          memory to handle the query. If you suspect this is the case,
          try adding <span class="command"><strong>ulimit -d 256000</strong></span> to the
          beginning of the <a class="link" href="programs.html#mysqld-safe" title="4.3.2 mysqld_safe — MySQL Server Startup Script"><span class="command"><strong>mysqld_safe</strong></span></a> script and
          restarting <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="communication-errors"></a>B.4.2.10 Communication Errors and Aborted Connections</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183900832"></a><a class="indexterm" name="idm46734183899792"></a><a class="indexterm" name="idm46734183898720"></a><p>
          If connection problems occur such as communication errors or
          aborted connections, use these sources of information to
          diagnose problems:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              The error log. See <a class="xref" href="server-administration.html#error-log" title="5.4.2 The Error Log">Section 5.4.2, “The Error Log”</a>.
            </p></li><li class="listitem"><p>
              The general query log. See <a class="xref" href="server-administration.html#query-log" title="5.4.3 The General Query Log">Section 5.4.3, “The General Query Log”</a>.
            </p></li><li class="listitem"><p>
              The
              <code class="literal">Aborted_<em class="replaceable"><code>xxx</code></em></code>
              and
              <code class="literal">Connection_errors_<em class="replaceable"><code>xxx</code></em></code>
              status variables. See
              <a class="xref" href="server-administration.html#server-status-variables" title="5.1.9 Server Status Variables">Section 5.1.9, “Server Status Variables”</a>.
            </p></li><li class="listitem"><p>
              The host cache, which is accessible using the Performance
              Schema <a class="link" href="performance-schema.html#host-cache-table" title="25.12.16.1 The host_cache Table"><code class="literal">host_cache</code></a> table. See
              <a class="xref" href="server-administration.html#host-cache" title="5.1.11.2 DNS Lookups and the Host Cache">Section 5.1.11.2, “DNS Lookups and the Host Cache”</a>, and
              <a class="xref" href="performance-schema.html#host-cache-table" title="25.12.16.1 The host_cache Table">Section 25.12.16.1, “The host_cache Table”</a>.
</p></li></ul>
</div>
<p>
          If the <a class="link" href="server-administration.html#sysvar_log_error_verbosity"><code class="literal">log_error_verbosity</code></a>
          system variable is set to 3, you might find messages like this
          in your error log:
        </p><pre data-lang="none" class="programlisting">[Note] Aborted connection 854 to db: 'employees' user: 'josh'</pre><p>
          If a client is unable even to connect, the server increments
          the <a class="link" href="server-administration.html#statvar_Aborted_connects"><code class="literal">Aborted_connects</code></a> status
          variable. Unsuccessful connection attempts can occur for the
          following reasons:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              A client attempts to access a database but has no
              privileges for it.
            </p></li><li class="listitem"><p>
              A client uses an incorrect password.
            </p></li><li class="listitem"><p>
              A connection packet does not contain the right
              information.
            </p></li><li class="listitem"><p>
              It takes more than
              <a class="link" href="server-administration.html#sysvar_connect_timeout"><code class="literal">connect_timeout</code></a> seconds
              to obtain a connect packet. See
              <a class="xref" href="server-administration.html#server-system-variables" title="5.1.7 Server System Variables">Section 5.1.7, “Server System Variables”</a>.
</p></li></ul>
</div>
<p>
          If these kinds of things happen, it might indicate that
          someone is trying to break into your server! If the general
          query log is enabled, messages for these types of problems are
          logged to it.
        </p><p>
          If a client successfully connects but later disconnects
          improperly or is terminated, the server increments the
          <a class="link" href="server-administration.html#statvar_Aborted_clients"><code class="literal">Aborted_clients</code></a> status
          variable, and logs an <span class="errortext">Aborted
          connection</span> message to the error log. The cause can
          be any of the following:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              The client program did not call
              <a class="link" href="connectors-apis.html#mysql-close" title="27.7.6.5 mysql_close()"><code class="literal">mysql_close()</code></a> before
              exiting.
            </p></li><li class="listitem"><p>
              The client had been sleeping more than
              <a class="link" href="server-administration.html#sysvar_wait_timeout"><code class="literal">wait_timeout</code></a> or
              <a class="link" href="server-administration.html#sysvar_interactive_timeout"><code class="literal">interactive_timeout</code></a>
              seconds without issuing any requests to the server. See
              <a class="xref" href="server-administration.html#server-system-variables" title="5.1.7 Server System Variables">Section 5.1.7, “Server System Variables”</a>.
            </p></li><li class="listitem"><p>
              The client program ended abruptly in the middle of a data
              transfer.
</p></li></ul>
</div>
<p>
          Other reasons for problems with aborted connections or aborted
          clients:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              The <a class="link" href="server-administration.html#sysvar_max_allowed_packet"><code class="literal">max_allowed_packet</code></a>
              variable value is too small or queries require more memory
              than you have allocated for <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>. See
              <a class="xref" href="error-handling.html#packet-too-large" title="B.4.2.9 Packet Too Large">Section B.4.2.9, “Packet Too Large”</a>.
            </p></li><li class="listitem"><p>
              Use of Ethernet protocol with Linux, both half and full
              duplex. Some Linux Ethernet drivers have this bug. You
              should test for this bug by transferring a huge file using
              FTP between the client and server machines. If a transfer
              goes in burst-pause-burst-pause mode, you are experiencing
              a Linux duplex syndrome. Switch the duplex mode for both
              your network card and hub/switch to either full duplex or
              to half duplex and test the results to determine the best
              setting.
            </p></li><li class="listitem"><p>
              A problem with the thread library that causes interrupts
              on reads.
            </p></li><li class="listitem"><p>
              Badly configured TCP/IP.
            </p></li><li class="listitem"><p>
              Faulty Ethernets, hubs, switches, cables, and so forth.
              This can be diagnosed properly only by replacing hardware.
</p></li></ul>
</div>
<p>
          See also <a class="xref" href="error-handling.html#gone-away" title="B.4.2.8 MySQL server has gone away">Section B.4.2.8, “MySQL server has gone away”</a>.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="full-table"></a>B.4.2.11 The table is full</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183854064"></a><p>
          If a table-full error occurs, it may be that the disk is full
          or that the table has reached its maximum size. The effective
          maximum table size for MySQL databases is usually determined
          by operating system constraints on file sizes, not by MySQL
          internal limits. See <a class="xref" href="optimization.html#table-size-limit" title="8.4.6 Limits on Table Size">Section 8.4.6, “Limits on Table Size”</a>.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="cannot-create"></a>B.4.2.12 Can't create/write to file</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183850208"></a><p>
          If you get an error of the following type for some queries, it
          means that MySQL cannot create a temporary file for the result
          set in the temporary directory:
        </p><pre data-lang="none" class="programlisting">Can't create/write to file '\\sqla3fe_0.ism'.</pre><p>
          The preceding error is a typical message for Windows; the Unix
          message is similar.
        </p><p>
          One fix is to start <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> with the
          <a class="link" href="server-administration.html#option_mysqld_tmpdir"><code class="option">--tmpdir</code></a> option or to add the
          option to the <code class="literal">[mysqld]</code> section of your
          option file. For example, to specify a directory of
          <code class="filename">C:\temp</code>, use these lines:
        </p><pre data-lang="ini" class="programlisting">[mysqld]
tmpdir=C:/temp</pre><p>
          The <code class="filename">C:\temp</code> directory must exist and have
          sufficient space for the MySQL server to write to. See
          <a class="xref" href="programs.html#option-files" title="4.2.2.2 Using Option Files">Section 4.2.2.2, “Using Option Files”</a>.
        </p><p>
          Another cause of this error can be permissions issues. Make
          sure that the MySQL server can write to the
          <a class="link" href="server-administration.html#sysvar_tmpdir"><code class="literal">tmpdir</code></a> directory.
        </p><p>
          Check also the error code that you get with
          <a class="link" href="programs.html#perror" title="4.8.2 perror — Display MySQL Error Message Information"><span class="command"><strong>perror</strong></span></a>. One reason the server cannot write
          to a table is that the file system is full:
        </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>perror 28</code></strong>
OS error code  28:  No space left on device
</pre><p>
          If you get an error of the following type during startup, it
          indicates that the file system or directory used for storing
          data files is write protected. Provided that the write error
          is to a test file, the error is not serious and can be safely
          ignored.
</p><pre data-lang="none" class="programlisting">Can't create test file /usr/local/mysql/data/master.lower-test</pre>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="commands-out-of-sync"></a>B.4.2.13 Commands out of sync</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183831824"></a><p>
          If you get <code class="literal">Commands out of sync; you can't run this
          command now</code> in your client code, you are calling
          client functions in the wrong order.
        </p><p>
          This can happen, for example, if you are using
          <a class="link" href="connectors-apis.html#mysql-use-result" title="27.7.6.77 mysql_use_result()"><code class="literal">mysql_use_result()</code></a> and try to
          execute a new query before you have called
          <a class="link" href="connectors-apis.html#mysql-free-result" title="27.7.6.25 mysql_free_result()"><code class="literal">mysql_free_result()</code></a>. It can
          also happen if you try to execute two queries that return data
          without calling
          <a class="link" href="connectors-apis.html#mysql-use-result" title="27.7.6.77 mysql_use_result()"><code class="literal">mysql_use_result()</code></a> or
          <a class="link" href="connectors-apis.html#mysql-store-result" title="27.7.6.75 mysql_store_result()"><code class="literal">mysql_store_result()</code></a> in
          between.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="ignoring-user"></a>B.4.2.14 Ignoring user</h4>

</div>

</div>

</div>
<p>
          If you get the following error, it means that when
          <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> was started or when it reloaded the
          grant tables, it found an account in the
          <code class="literal">user</code> table that had an invalid password.
        </p><p>
          <code class="literal">Found wrong password for user
          '<em class="replaceable"><code>some_user</code></em>'@'<em class="replaceable"><code>some_host</code></em>';
          ignoring user</code>
        </p><p>
          As a result, the account is simply ignored by the permission
          system.
        </p><p>
          The following list indicates possible causes of and fixes for
          this problem:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              You may be running a new version of
              <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> with an old
              <code class="literal">user</code> table. Check whether the
              <code class="literal">Password</code> column of that table is
              shorter than 16 characters. If so, correct this condition
              by running <a class="link" href="programs.html#mysql-upgrade" title="4.4.7 mysql_upgrade — Check and Upgrade MySQL Tables"><span class="command"><strong>mysql_upgrade</strong></span></a>.
            </p></li><li class="listitem"><p>
              The account has an old password (eight characters long).
              Update the account in the <code class="literal">user</code> table to
              have a new password.
            </p></li><li class="listitem"><p>
              <a class="indexterm" name="idm46734183809760"></a>

              You have specified a password in the
              <code class="literal">user</code> table without using the
              <a class="link" href="functions.html#function_password"><code class="literal">PASSWORD()</code></a> function. Use
              <a class="link" href="programs.html#mysql" title="4.5.1 mysql — The MySQL Command-Line Client"><span class="command"><strong>mysql</strong></span></a> to update the account in the
              <code class="literal">user</code> table with a new password, making
              sure to use the <a class="link" href="functions.html#function_password"><code class="literal">PASSWORD()</code></a>
              function:
            </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>UPDATE user SET Password=PASSWORD('<em class="replaceable"><code>new_password</code></em>')</code></strong>
    -&gt; <strong class="userinput"><code>WHERE User='<em class="replaceable"><code>some_user</code></em>' AND Host='<em class="replaceable"><code>some_host</code></em>';</code></strong>
</pre></li></ul>
</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="cannot-find-table"></a>B.4.2.15 Table 'tbl_name' doesn't exist</h4>

</div>

</div>

</div>
<p>
          If you get either of the following errors, it usually means
          that no table exists in the default database with the given
          name:
        </p><pre data-lang="none" class="programlisting">Table '<em class="replaceable"><code>tbl_name</code></em>' doesn't exist
Can't find file: '<em class="replaceable"><code>tbl_name</code></em>' (errno: 2)
</pre><p>
          In some cases, it may be that the table does exist but that
          you are referring to it incorrectly:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              Because MySQL uses directories and files to store
              databases and tables, database and table names are
              case-sensitive if they are located on a file system that
              has case-sensitive file names.
            </p></li><li class="listitem"><p>
              Even for file systems that are not case-sensitive, such as
              on Windows, all references to a given table within a query
              must use the same lettercase.
</p></li></ul>
</div>
<p>
          You can check which tables are in the default database with
          <a class="link" href="sql-statements.html#show-tables" title="13.7.5.37 SHOW TABLES Statement"><code class="literal">SHOW TABLES</code></a>. See
          <a class="xref" href="sql-statements.html#show" title="13.7.5 SHOW Statements">Section 13.7.5, “SHOW Statements”</a>.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="cannot-initialize-character-set"></a>B.4.2.16 Can't initialize character set</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183788944"></a><p>
          You might see an error like this if you have character set
          problems:
        </p><pre data-lang="none" class="programlisting">MySQL Connection Failed: Can't initialize character set <em class="replaceable"><code>charset_name</code></em>
</pre><p>
          This error can have any of the following causes:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              The character set is a multibyte character set and you
              have no support for the character set in the client. In
              this case, you need to recompile the client by running
              <span class="command"><strong>CMake</strong></span> with the
              <a class="link" href="installing.html#option_cmake_default_charset"><code class="option">-DDEFAULT_CHARSET=<em class="replaceable"><code>charset_name</code></em></code></a>
              or
              <a class="link" href="installing.html#option_cmake_with_extra_charsets"><code class="option">-DWITH_EXTRA_CHARSETS=<em class="replaceable"><code>charset_name</code></em></code></a>
              option. See
              <a class="xref" href="installing.html#source-configuration-options" title="2.9.7 MySQL Source-Configuration Options">Section 2.9.7, “MySQL Source-Configuration Options”</a>.
            </p><p>
              All standard MySQL binaries are compiled with
              <a class="link" href="installing.html#option_cmake_with_extra_charsets"><code class="option">-DWITH_EXTRA_CHARSETS=complex</code></a>,
              which enables support for all multibyte character sets.
              See <a class="xref" href="installing.html#source-configuration-options" title="2.9.7 MySQL Source-Configuration Options">Section 2.9.7, “MySQL Source-Configuration Options”</a>.
            </p></li><li class="listitem"><p>
              The character set is a simple character set that is not
              compiled into <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>, and the character
              set definition files are not in the place where the client
              expects to find them.
            </p><p>
              In this case, you need to use one of the following methods
              to solve the problem:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p>
                  Recompile the client with support for the character
                  set. See
                  <a class="xref" href="installing.html#source-configuration-options" title="2.9.7 MySQL Source-Configuration Options">Section 2.9.7, “MySQL Source-Configuration Options”</a>.
                </p></li><li class="listitem"><p>
                  Specify to the client the directory where the
                  character set definition files are located. For many
                  clients, you can do this with the
                  <code class="option">--character-sets-dir</code> option.
                </p></li><li class="listitem"><p>
                  Copy the character definition files to the path where
                  the client expects them to be.
</p></li></ul>
</div>
</li></ul>
</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="not-enough-file-handles"></a>B.4.2.17 File Not Found and Similar Errors</h4>

</div>

</div>

</div>
<p>
          If you get <code class="literal">ERROR
          '<em class="replaceable"><code>file_name</code></em>' not found (errno:
          23)</code>, <code class="literal">Can't open file:
          <em class="replaceable"><code>file_name</code></em> (errno: 24)</code>, or
          any other error with <code class="literal">errno 23</code> or
          <code class="literal">errno 24</code> from MySQL, it means that you have
          not allocated enough file descriptors for the MySQL server.
          You can use the <a class="link" href="programs.html#perror" title="4.8.2 perror — Display MySQL Error Message Information"><span class="command"><strong>perror</strong></span></a> utility to get a
          description of what the error number means:
        </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>perror 23</code></strong>
OS error code  23:  File table overflow
shell&gt; <strong class="userinput"><code>perror 24</code></strong>
OS error code  24:  Too many open files
shell&gt; <strong class="userinput"><code>perror 11</code></strong>
OS error code  11:  Resource temporarily unavailable
</pre><p>
          The problem here is that <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> is trying
          to keep open too many files simultaneously. You can either
          tell <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> not to open so many files at
          once or increase the number of file descriptors available to
          <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>.
        </p><p>
          To tell <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> to keep open fewer files at
          a time, you can make the table cache smaller by reducing the
          value of the <a class="link" href="server-administration.html#sysvar_table_open_cache"><code class="literal">table_open_cache</code></a>
          system variable (the default value is 64). This may not
          entirely prevent running out of file descriptors because in
          some circumstances the server may attempt to extend the cache
          size temporarily, as described in
          <a class="xref" href="optimization.html#table-cache" title="8.4.3.1 How MySQL Opens and Closes Tables">Section 8.4.3.1, “How MySQL Opens and Closes Tables”</a>. Reducing the value of
          <a class="link" href="server-administration.html#sysvar_max_connections"><code class="literal">max_connections</code></a> also reduces
          the number of open files (the default value is 100).
        </p><a class="indexterm" name="idm46734183750928"></a><p>
          To change the number of file descriptors available to
          <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>, you can use the
          <a class="link" href="programs.html#option_mysqld_safe_open-files-limit"><code class="option">--open-files-limit</code></a> option
          to <a class="link" href="programs.html#mysqld-safe" title="4.3.2 mysqld_safe — MySQL Server Startup Script"><span class="command"><strong>mysqld_safe</strong></span></a> or set the
          <a class="link" href="server-administration.html#sysvar_open_files_limit"><code class="literal">open_files_limit</code></a> system
          variable. See <a class="xref" href="server-administration.html#server-system-variables" title="5.1.7 Server System Variables">Section 5.1.7, “Server System Variables”</a>. The
          easiest way to set these values is to add an option to your
          option file. See <a class="xref" href="programs.html#option-files" title="4.2.2.2 Using Option Files">Section 4.2.2.2, “Using Option Files”</a>. If you have
          an old version of <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> that does not
          support setting the open files limit, you can edit the
          <a class="link" href="programs.html#mysqld-safe" title="4.3.2 mysqld_safe — MySQL Server Startup Script"><span class="command"><strong>mysqld_safe</strong></span></a> script. There is a
          commented-out line <span class="command"><strong>ulimit -n 256</strong></span> in the
          script. You can remove the <code class="literal">#</code> character to
          uncomment this line, and change the number
          <code class="literal">256</code> to set the number of file descriptors
          to be made available to <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>.
        </p><p>
          <a class="link" href="programs.html#option_mysqld_safe_open-files-limit"><code class="option">--open-files-limit</code></a> and
          <span class="command"><strong>ulimit</strong></span> can increase the number of file
          descriptors, but only up to the limit imposed by the operating
          system. There is also a <span class="quote">“<span class="quote">hard</span>”</span> limit that can be
          overridden only if you start <a class="link" href="programs.html#mysqld-safe" title="4.3.2 mysqld_safe — MySQL Server Startup Script"><span class="command"><strong>mysqld_safe</strong></span></a> or
          <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> as <code class="literal">root</code> (just
          remember that you also need to start the server with the
          <a class="link" href="server-administration.html#option_mysqld_user"><code class="option">--user</code></a> option in this case so
          that it does not continue to run as <code class="literal">root</code>
          after it starts up). If you need to increase the operating
          system limit on the number of file descriptors available to
          each process, consult the documentation for your system.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">

<div class="admon-title">
Note
</div>
<p>
            If you run the <span class="command"><strong>tcsh</strong></span> shell,
            <span class="command"><strong>ulimit</strong></span> does not work!
            <span class="command"><strong>tcsh</strong></span> also reports incorrect values when
            you ask for the current limits. In this case, you should
            start <a class="link" href="programs.html#mysqld-safe" title="4.3.2 mysqld_safe — MySQL Server Startup Script"><span class="command"><strong>mysqld_safe</strong></span></a> using
            <span class="command"><strong>sh</strong></span>.
</p>
</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="table-corruption"></a>B.4.2.18 Table-Corruption Issues</h4>

</div>

</div>

</div>
<p>
          If you have started <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> with the
          <a class="link" href="server-administration.html#sysvar_myisam_recover_options"><code class="literal">myisam_recover_options</code></a> system
          variable set, MySQL automatically checks and tries to repair
          <code class="literal">MyISAM</code> tables if they are marked as 'not
          closed properly' or 'crashed'. If this happens, MySQL writes
          an entry in the <code class="literal">hostname.err</code> file
          <code class="literal">'Warning: Checking table ...'</code> which is
          followed by <code class="literal">Warning: Repairing table</code> if the
          table needs to be repaired. If you get a lot of these errors,
          without <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> having died unexpectedly
          just before, then something is wrong and needs to be
          investigated further.
        </p><p>
          When the server detects <code class="literal">MyISAM</code> table
          corruption, it writes additional information to the error log,
          such as the name and line number of the source file, and the
          list of threads accessing the table. Example: <code class="literal">Got an
          error from thread_id=1, mi_dynrec.c:368</code>. This is
          useful information to include in bug reports.
        </p><p>
          See also <a class="xref" href="server-administration.html#server-options" title="5.1.6 Server Command Options">Section 5.1.6, “Server Command Options”</a>, and
          <a class="xref" href="extending-mysql.html#reproducible-test-case" title="28.5.1.7 Making a Test Case If You Experience Table Corruption">Section 28.5.1.7, “Making a Test Case If You Experience Table Corruption”</a>.
</p>
</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="administration-issues"></a>B.4.3 Administration-Related Issues</h3>

</div>

</div>

</div>
<div class="toc">
<dl class="toc"><dt><span class="section"><a href="error-handling.html#file-permissions">B.4.3.1 Problems with File Permissions</a></span></dt><dt><span class="section"><a href="error-handling.html#resetting-permissions">B.4.3.2 How to Reset the Root Password</a></span></dt><dt><span class="section"><a href="error-handling.html#crashing">B.4.3.3 What to Do If MySQL Keeps Crashing</a></span></dt><dt><span class="section"><a href="error-handling.html#full-disk">B.4.3.4 How MySQL Handles a Full Disk</a></span></dt><dt><span class="section"><a href="error-handling.html#temporary-files">B.4.3.5 Where MySQL Stores Temporary Files</a></span></dt><dt><span class="section"><a href="error-handling.html#problems-with-mysql-sock">B.4.3.6 How to Protect or Change the MySQL Unix Socket File</a></span></dt><dt><span class="section"><a href="error-handling.html#timezone-problems">B.4.3.7 Time Zone Problems</a></span></dt></dl>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="file-permissions"></a>B.4.3.1 Problems with File Permissions</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183708896"></a><a class="indexterm" name="idm46734183707440"></a><a class="indexterm" name="idm46734183705952"></a><a class="indexterm" name="idm46734183704464"></a><a class="indexterm" name="idm46734183703376"></a><p>
          If you have problems with file permissions, the
          <code class="literal">UMASK</code> or <code class="literal">UMASK_DIR</code>
          environment variable might be set incorrectly when
          <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> starts. For example,
          <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> might issue the following error
          message when you create a table:
        </p><pre data-lang="none" class="programlisting">ERROR: Can't find file: 'path/with/filename.frm' (Errcode: 13)</pre><p>
          The default <code class="literal">UMASK</code> and
          <code class="literal">UMASK_DIR</code> values are
          <code class="literal">0640</code> and <code class="literal">0750</code>,
          respectively. <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> assumes that the value
          for <code class="literal">UMASK</code> or <code class="literal">UMASK_DIR</code>
          is in octal if it starts with a zero. For example, setting
          <code class="literal">UMASK=0600</code> is equivalent to
          <code class="literal">UMASK=384</code> because 0600 octal is 384
          decimal.
        </p><p>
          Assuming that you start <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> using
          <a class="link" href="programs.html#mysqld-safe" title="4.3.2 mysqld_safe — MySQL Server Startup Script"><span class="command"><strong>mysqld_safe</strong></span></a>, change the default
          <code class="literal">UMASK</code> value as follows:
        </p><pre data-lang="terminal" class="programlisting">UMASK=384  # = 600 in octal
export UMASK
mysqld_safe &amp;</pre>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">

<div class="admon-title">
Note
</div>
<p>
            An exception applies for the error log file if you start
            <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> using
            <a class="link" href="programs.html#mysqld-safe" title="4.3.2 mysqld_safe — MySQL Server Startup Script"><span class="command"><strong>mysqld_safe</strong></span></a>, which does not respect
            <code class="literal">UMASK</code>: <a class="link" href="programs.html#mysqld-safe" title="4.3.2 mysqld_safe — MySQL Server Startup Script"><span class="command"><strong>mysqld_safe</strong></span></a> may
            create the error log file if it does not exist prior to
            starting <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>, and
            <a class="link" href="programs.html#mysqld-safe" title="4.3.2 mysqld_safe — MySQL Server Startup Script"><span class="command"><strong>mysqld_safe</strong></span></a> uses a umask set to a strict
            value of <code class="literal">0137</code>. If this is unsuitable,
            create the error file manually with the desired access mode
            prior to executing <a class="link" href="programs.html#mysqld-safe" title="4.3.2 mysqld_safe — MySQL Server Startup Script"><span class="command"><strong>mysqld_safe</strong></span></a>.
</p>
</div>
<a class="indexterm" name="idm46734183674208"></a><a class="indexterm" name="idm46734183673120"></a><p>
          By default, <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> creates database
          directories with an access permission value of
          <code class="literal">0750</code>. To modify this behavior, set the
          <code class="literal">UMASK_DIR</code> variable. If you set its value,
          new directories are created with the combined
          <code class="literal">UMASK</code> and <code class="literal">UMASK_DIR</code>
          values. For example, to give group access to all new
          directories, start <a class="link" href="programs.html#mysqld-safe" title="4.3.2 mysqld_safe — MySQL Server Startup Script"><span class="command"><strong>mysqld_safe</strong></span></a> as follows:
        </p><pre data-lang="terminal" class="programlisting">UMASK_DIR=504  # = 770 in octal
export UMASK_DIR
mysqld_safe &amp;</pre><p>
          For additional details, see
          <a class="xref" href="programs.html#environment-variables" title="4.9 Environment Variables">Section 4.9, “Environment Variables”</a>.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="resetting-permissions"></a>B.4.3.2 How to Reset the Root Password</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183662208"></a><a class="indexterm" name="idm46734183660752"></a><a class="indexterm" name="idm46734183659264"></a><a class="indexterm" name="idm46734183657776"></a><p>
          If you have never assigned a <code class="literal">root</code> password
          for MySQL, the server does not require a password at all for
          connecting as <code class="literal">root</code>. However, this is
          insecure. For instructions on assigning a password, see
          <a class="xref" href="installing.html#default-privileges" title="2.10.4 Securing the Initial MySQL Account">Section 2.10.4, “Securing the Initial MySQL Account”</a>.
        </p><p>
          If you know the <code class="literal">root</code> password and want to
          change it, see <a class="xref" href="sql-statements.html#alter-user" title="13.7.1.1 ALTER USER Statement">Section 13.7.1.1, “ALTER USER Statement”</a>, and
          <a class="xref" href="sql-statements.html#set-password" title="13.7.1.7 SET PASSWORD Statement">Section 13.7.1.7, “SET PASSWORD Statement”</a>.
        </p><p>
          If you assigned a <code class="literal">root</code> password previously
          but have forgotten it, you can assign a new password. The
          following sections provide instructions for Windows and Unix
          and Unix-like systems, as well as generic instructions that
          apply to any system.
</p>
<div class="section">

<div class="titlepage">
<div>
<div>
<h5 class="title"><a name="resetting-permissions-windows"></a>B.4.3.2.1 Resetting the Root Password: Windows Systems</h5>
</div>
</div>
</div>
<p>
            On Windows, use the following procedure to reset the
            password for the MySQL <code class="literal">'root'@'localhost'</code>
            account. To change the password for a
            <code class="literal">root</code> account with a different host name
            part, modify the instructions to use that host name.
</p>
<div class="orderedlist">
<ol class="orderedlist" type="1"><li class="listitem"><p>
                Log on to your system as Administrator.
              </p></li><li class="listitem"><p>
                Stop the MySQL server if it is running. For a server
                that is running as a Windows service, go to the Services
                manager: From the <span class="guimenu">Start</span> menu, select
                <span class="guisubmenu">Control Panel</span>, then
                <span class="guisubmenu">Administrative Tools</span>, then
                <span class="guimenuitem">Services</span>. Find the MySQL
                service in the list and stop it.
              </p><p>
                If your server is not running as a service, you may need
                to use the Task Manager to force it to stop.
              </p></li><li class="listitem"><p>
                Create a text file containing the password-assignment
                statement on a single line. Replace the password with
                the password that you want to use.
              </p><pre data-lang="sql" class="programlisting">ALTER USER 'root'@'localhost' IDENTIFIED BY 'MyNewPass';</pre></li><li class="listitem"><p>
                Save the file. This example assumes that you name the
                file <code class="filename">C:\mysql-init.txt</code>.
              </p></li><li class="listitem"><p>
                Open a console window to get to the command prompt: From
                the <span class="guimenu">Start</span> menu, select
                <span class="guisubmenu">Run</span>, then enter
                <span class="command"><strong>cmd</strong></span> as the command to be run.
              </p></li><li class="listitem"><p>
                Start the MySQL server with the
                <a class="link" href="server-administration.html#sysvar_init_file"><code class="literal">init_file</code></a> system
                variable set to name the file (notice that the backslash
                in the option value is doubled):
              </p><pre data-lang="terminal" class="programlisting">C:\&gt; <strong class="userinput"><code>cd "C:\Program Files\MySQL\MySQL Server 5.7\bin"</code></strong>
C:\&gt; <strong class="userinput"><code>mysqld --init-file=C:\\mysql-init.txt</code></strong>
</pre><p>
                If you installed MySQL to a different location, adjust
                the <span class="command"><strong>cd</strong></span> command accordingly.
              </p><p>
                The server executes the contents of the file named by
                the <a class="link" href="server-administration.html#sysvar_init_file"><code class="literal">init_file</code></a> system
                variable at startup, changing the
                <code class="literal">'root'@'localhost'</code> account password.
              </p><p>
                To have server output to appear in the console window
                rather than in a log file, add the
                <a class="link" href="server-administration.html#option_mysqld_console"><code class="option">--console</code></a> option to the
                <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> command.
              </p><p>
                If you installed MySQL using the MySQL Installation
                Wizard, you may need to specify a
                <a class="link" href="programs.html#option_general_defaults-file"><code class="option">--defaults-file</code></a> option.
                For example:
              </p><pre data-lang="terminal" class="programlisting">C:\&gt; <strong class="userinput"><code>mysqld</code></strong>
         <strong class="userinput"><code>--defaults-file="C:\\ProgramData\\MySQL\\MySQL Server 5.7\\my.ini"</code></strong>
         <strong class="userinput"><code>--init-file=C:\\mysql-init.txt</code></strong>
</pre><p>
                The appropriate
                <a class="link" href="programs.html#option_general_defaults-file"><code class="option">--defaults-file</code></a> setting
                can be found using the Services Manager: From the
                <span class="guimenu">Start</span> menu, select
                <span class="guisubmenu">Control Panel</span>, then
                <span class="guisubmenu">Administrative Tools</span>, then
                <span class="guimenuitem">Services</span>. Find the MySQL
                service in the list, right-click it, and choose the
                <code class="literal">Properties</code> option. The <code class="literal">Path
                to executable</code> field contains the
                <a class="link" href="programs.html#option_general_defaults-file"><code class="option">--defaults-file</code></a> setting.
              </p></li><li class="listitem"><p>
                After the server has started successfully, delete
                <code class="filename">C:\mysql-init.txt</code>.
</p></li></ol>
</div>
<p>
            You should now be able to connect to the MySQL server as
            <code class="literal">root</code> using the new password. Stop the
            MySQL server and restart it normally. If you run the server
            as a service, start it from the Windows Services window. If
            you start the server manually, use whatever command you
            normally use.
          </p><p>
            If the <a class="link" href="sql-statements.html#alter-user" title="13.7.1.1 ALTER USER Statement"><code class="literal">ALTER USER</code></a> statement
            fails to reset the password, try repeating the procedure
            using the following statements to modify the
            <code class="literal">user</code> table directly:
          </p><pre data-lang="sql" class="programlisting">UPDATE mysql.user
    SET authentication_string = PASSWORD('MyNewPass'), password_expired = 'N'
    WHERE User = 'root' AND Host = 'localhost';
FLUSH PRIVILEGES;</pre>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h5 class="title"><a name="resetting-permissions-unix"></a>B.4.3.2.2 Resetting the Root Password: Unix and Unix-Like Systems</h5>

</div>

</div>

</div>
<p>
            On Unix, use the following procedure to reset the password
            for the MySQL <code class="literal">'root'@'localhost'</code> account.
            To change the password for a <code class="literal">root</code> account
            with a different host name part, modify the instructions to
            use that host name.
          </p><p>
            The instructions assume that you will start the MySQL server
            from the Unix login account that you normally use for
            running it. For example, if you run the server using the
            <code class="literal">mysql</code> login account, you should log in as
            <code class="literal">mysql</code> before using the instructions.
            Alternatively, you can log in as <code class="literal">root</code>,
            but in this case you <span class="emphasis"><em>must</em></span> start
            <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> with the
            <a class="link" href="server-administration.html#option_mysqld_user"><code class="option">--user=mysql</code></a> option. If you
            start the server as <code class="literal">root</code> without using
            <a class="link" href="server-administration.html#option_mysqld_user"><code class="option">--user=mysql</code></a>, the server may
            create <code class="literal">root</code>-owned files in the data
            directory, such as log files, and these may cause
            permission-related problems for future server startups. If
            that happens, you will need to either change the ownership
            of the files to <code class="literal">mysql</code> or remove them.
</p>
<div class="orderedlist">
<ol class="orderedlist" type="1"><li class="listitem"><p>
                Log on to your system as the Unix user that the MySQL
                server runs as (for example, <code class="literal">mysql</code>).
              </p></li><li class="listitem"><p>
                Stop the MySQL server if it is running. Locate the
                <code class="filename">.pid</code> file that contains the
                server's process ID. The exact location and name of this
                file depend on your distribution, host name, and
                configuration. Common locations are
                <code class="filename">/var/lib/mysql/</code>,
                <code class="filename">/var/run/mysqld/</code>, and
                <code class="filename">/usr/local/mysql/data/</code>. Generally,
                the file name has an extension of
                <code class="filename">.pid</code> and begins with either
                <code class="filename">mysqld</code> or your system's host name.
              </p><p>
                Stop the MySQL server by sending a normal
                <code class="literal">kill</code> (not <code class="literal">kill -9</code>)
                to the <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> process. Use the actual
                path name of the <code class="filename">.pid</code> file in the
                following command:
              </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>kill `cat /mysql-data-directory/host_name.pid`</code></strong>
</pre><p>
                Use backticks (not forward quotation marks) with the
                <code class="literal">cat</code> command. These cause the output
                of <code class="literal">cat</code> to be substituted into the
                <code class="literal">kill</code> command.
              </p></li><li class="listitem"><p>
                Create a text file containing the password-assignment
                statement on a single line. Replace the password with
                the password that you want to use.
              </p><pre data-lang="sql" class="programlisting">ALTER USER 'root'@'localhost' IDENTIFIED BY 'MyNewPass';</pre></li><li class="listitem"><p>
                Save the file. This example assumes that you name the
                file <code class="filename">/home/me/mysql-init</code>. The file
                contains the password, so do not save it where it can be
                read by other users. If you are not logged in as
                <code class="literal">mysql</code> (the user the server runs as),
                make sure that the file has permissions that permit
                <code class="literal">mysql</code> to read it.
              </p></li><li class="listitem"><p>
                Start the MySQL server with the
                <a class="link" href="server-administration.html#sysvar_init_file"><code class="literal">init_file</code></a> system
                variable set to name the file:
              </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>mysqld --init-file=/home/me/mysql-init &amp;</code></strong>
</pre><p>
                The server executes the contents of the file named by
                the <a class="link" href="server-administration.html#sysvar_init_file"><code class="literal">init_file</code></a> system
                variable at startup, changing the
                <code class="literal">'root'@'localhost'</code> account password.
              </p><p>
                Other options may be necessary as well, depending on how
                you normally start your server. For example,
                <a class="link" href="programs.html#option_general_defaults-file"><code class="option">--defaults-file</code></a> may be
                needed before the
                <a class="link" href="server-administration.html#sysvar_init_file"><code class="literal">init_file</code></a> argument.
              </p></li><li class="listitem"><p>
                After the server has started successfully, delete
                <code class="filename">/home/me/mysql-init</code>.
</p></li></ol>
</div>
<p>
            You should now be able to connect to the MySQL server as
            <code class="literal">root</code> using the new password. Stop the
            server and restart it normally.
          </p><p>
            If the <a class="link" href="sql-statements.html#alter-user" title="13.7.1.1 ALTER USER Statement"><code class="literal">ALTER USER</code></a> statement
            fails to reset the password, try repeating the procedure
            using the following statements to modify the
            <code class="literal">user</code> table directly:
          </p><pre data-lang="sql" class="programlisting">UPDATE mysql.user
    SET authentication_string = PASSWORD('MyNewPass'), password_expired = 'N'
    WHERE User = 'root' AND Host = 'localhost';
FLUSH PRIVILEGES;</pre>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h5 class="title"><a name="resetting-permissions-generic"></a>B.4.3.2.3 Resetting the Root Password: Generic Instructions</h5>

</div>

</div>

</div>
<p>
            The preceding sections provide password-resetting
            instructions specifically for Windows and Unix and Unix-like
            systems. Alternatively, on any platform, you can reset the
            password using the <a class="link" href="programs.html#mysql" title="4.5.1 mysql — The MySQL Command-Line Client"><span class="command"><strong>mysql</strong></span></a> client (but this
            approach is less secure):
</p>
<div class="orderedlist">
<ol class="orderedlist" type="1"><li class="listitem"><p>
                Stop the MySQL server if necessary, then restart it with
                the <a class="link" href="server-administration.html#option_mysqld_skip-grant-tables"><code class="option">--skip-grant-tables</code></a>
                option. This enables anyone to connect without a
                password and with all privileges, and disables
                account-management statements such as
                <a class="link" href="sql-statements.html#alter-user" title="13.7.1.1 ALTER USER Statement"><code class="literal">ALTER USER</code></a> and
                <a class="link" href="sql-statements.html#set-password" title="13.7.1.7 SET PASSWORD Statement"><code class="literal">SET PASSWORD</code></a>. Because
                this is insecure, you might want to use
                <a class="link" href="server-administration.html#option_mysqld_skip-grant-tables"><code class="option">--skip-grant-tables</code></a> in
                conjunction with enabling the
                <a class="link" href="server-administration.html#sysvar_skip_networking"><code class="literal">skip_networking</code></a> system
                variable to prevent remote clients from connecting.
              </p></li><li class="listitem"><p>
                Connect to the MySQL server using the
                <a class="link" href="programs.html#mysql" title="4.5.1 mysql — The MySQL Command-Line Client"><span class="command"><strong>mysql</strong></span></a> client; no password is
                necessary because the server was started with
                <a class="link" href="server-administration.html#option_mysqld_skip-grant-tables"><code class="option">--skip-grant-tables</code></a>:
              </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>mysql</code></strong>
</pre></li><li class="listitem"><p>
                In the <code class="literal">mysql</code> client, tell the server
                to reload the grant tables so that account-management
                statements work:
              </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>FLUSH PRIVILEGES;</code></strong>
</pre><p>
                Then change the <code class="literal">'root'@'localhost'</code>
                account password. Replace the password with the password
                that you want to use. To change the password for a
                <code class="literal">root</code> account with a different host
                name part, modify the instructions to use that host
                name.
              </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>ALTER USER 'root'@'localhost' IDENTIFIED BY 'MyNewPass';</code></strong>
</pre></li></ol>
</div>
<p>
            You should now be able to connect to the MySQL server as
            <code class="literal">root</code> using the new password. Stop the
            server and restart it normally (without the
            <a class="link" href="server-administration.html#option_mysqld_skip-grant-tables"><code class="option">--skip-grant-tables</code></a> option
            and without enabling the
            <a class="link" href="server-administration.html#sysvar_skip_networking"><code class="literal">skip_networking</code></a> system
            variable).
          </p><p>
            If the <a class="link" href="sql-statements.html#alter-user" title="13.7.1.1 ALTER USER Statement"><code class="literal">ALTER USER</code></a> statement
            fails to reset the password, try repeating the procedure
            using the following statements to modify the
            <code class="literal">user</code> table directly:
          </p><pre data-lang="sql" class="programlisting">UPDATE mysql.user SET authentication_string = PASSWORD('MyNewPass')
WHERE User = 'root' AND Host = 'localhost';
FLUSH PRIVILEGES;</pre>
</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="crashing"></a>B.4.3.3 What to Do If MySQL Keeps Crashing</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183523008"></a><p>
          Each MySQL version is tested on many platforms before it is
          released. This does not mean that there are no bugs in MySQL,
          but if there are bugs, they should be very few and can be hard
          to find. If you have a problem, it always helps if you try to
          find out exactly what crashes your system, because you have a
          much better chance of getting the problem fixed quickly.
        </p><p>
          First, you should try to find out whether the problem is that
          the <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> server dies or whether your
          problem has to do with your client. You can check how long
          your <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> server has been up by executing
          <a class="link" href="programs.html#mysqladmin" title="4.5.2 mysqladmin — Client for Administering a MySQL Server"><span class="command"><strong>mysqladmin version</strong></span></a>. If
          <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> has died and restarted, you may find
          the reason by looking in the server's error log. See
          <a class="xref" href="server-administration.html#error-log" title="5.4.2 The Error Log">Section 5.4.2, “The Error Log”</a>.
        </p><p>
          On some systems, you can find in the error log a stack trace
          of where <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> died that you can resolve
          with the <code class="literal">resolve_stack_dump</code> program. See
          <a class="xref" href="extending-mysql.html#porting" title="28.5 Debugging and Porting MySQL">Section 28.5, “Debugging and Porting MySQL”</a>. Note that the variable values
          written in the error log may not always be 100% correct.
        </p><p>
          Many server crashes are caused by corrupted data files or
          index files. MySQL updates the files on disk with the
          <code class="literal">write()</code> system call after every SQL
          statement and before the client is notified about the result.
          (This is not true if you are running with the
          <a class="link" href="server-administration.html#sysvar_delay_key_write"><code class="literal">delay_key_write</code></a> system
          variable enabled, in which case data files are written but not
          index files.) This means that data file contents are safe even
          if <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> crashes, because the operating
          system ensures that the unflushed data is written to disk. You
          can force MySQL to flush everything to disk after every SQL
          statement by starting <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> with the
          <a class="link" href="server-administration.html#option_mysqld_flush"><code class="option">--flush</code></a> option.
        </p><p>
          The preceding means that normally you should not get corrupted
          tables unless one of the following happens:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              The MySQL server or the server host was killed in the
              middle of an update.
            </p></li><li class="listitem"><p>
              You have found a bug in <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> that
              caused it to die in the middle of an update.
            </p></li><li class="listitem"><p>
              Some external program is manipulating data files or index
              files at the same time as <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>
              without locking the table properly.
            </p></li><li class="listitem"><p>
              You are running many <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> servers
              using the same data directory on a system that does not
              support good file system locks (normally handled by the
              <code class="literal">lockd</code> lock manager), or you are running
              multiple servers with external locking disabled.
            </p></li><li class="listitem"><p>
              You have a crashed data file or index file that contains
              very corrupt data that confused <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>.
            </p></li><li class="listitem"><p>
              You have found a bug in the data storage code. This isn't
              likely, but it is at least possible. In this case, you can
              try to change the storage engine to another engine by
              using <a class="link" href="sql-statements.html#alter-table" title="13.1.8 ALTER TABLE Statement"><code class="literal">ALTER TABLE</code></a> on a
              repaired copy of the table.
</p></li></ul>
</div>
<p>
          Because it is very difficult to know why something is
          crashing, first try to check whether things that work for
          others crash for you. Try the following things:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              Stop the <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> server with
              <a class="link" href="programs.html#mysqladmin" title="4.5.2 mysqladmin — Client for Administering a MySQL Server"><span class="command"><strong>mysqladmin shutdown</strong></span></a>, run
              <a class="link" href="programs.html#myisamchk" title="4.6.3 myisamchk — MyISAM Table-Maintenance Utility"><span class="command"><strong>myisamchk --silent --force */*.MYI</strong></span></a> from
              the data directory to check all <code class="literal">MyISAM</code>
              tables, and restart <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>. This
              ensures that you are running from a clean state. See
              <a class="xref" href="server-administration.html" title="Chapter 5 MySQL Server Administration">Chapter 5, <i>MySQL Server Administration</i></a>.
            </p></li><li class="listitem"><p>
              Start <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> with the general query log
              enabled (see <a class="xref" href="server-administration.html#query-log" title="5.4.3 The General Query Log">Section 5.4.3, “The General Query Log”</a>). Then try to
              determine from the information written to the log whether
              some specific query kills the server. About 95% of all
              bugs are related to a particular query. Normally, this is
              one of the last queries in the log file just before the
              server restarts. See <a class="xref" href="server-administration.html#query-log" title="5.4.3 The General Query Log">Section 5.4.3, “The General Query Log”</a>. If you
              can repeatedly kill MySQL with a specific query, even when
              you have checked all tables just before issuing it, then
              you have isolated the bug and should submit a bug report
              for it. See <a class="xref" href="introduction.html#bug-reports" title="1.7 How to Report Bugs or Problems">Section 1.7, “How to Report Bugs or Problems”</a>.
            </p></li><li class="listitem"><p>
              Try to make a test case that we can use to repeat the
              problem. See <a class="xref" href="extending-mysql.html#porting" title="28.5 Debugging and Porting MySQL">Section 28.5, “Debugging and Porting MySQL”</a>.
            </p></li><li class="listitem"><p>
              Try the <code class="literal">fork_big.pl</code> script. (It is
              located in the <code class="filename">tests</code> directory of
              source distributions.)
            </p></li><li class="listitem"><p>
              Configuring MySQL for debugging makes it much easier to
              gather information about possible errors if something goes
              wrong. Reconfigure MySQL with the
              <a class="link" href="installing.html#option_cmake_with_debug"><code class="option">-DWITH_DEBUG=1</code></a> option to
              <span class="command"><strong>CMake</strong></span> and then recompile. See
              <a class="xref" href="extending-mysql.html#porting" title="28.5 Debugging and Porting MySQL">Section 28.5, “Debugging and Porting MySQL”</a>.
            </p></li><li class="listitem"><p>
              Make sure that you have applied the latest patches for
              your operating system.
            </p></li><li class="listitem"><p>
              Use the
              <a class="link" href="server-administration.html#option_mysqld_external-locking"><code class="option">--skip-external-locking</code></a>
              option to <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>. On some systems, the
              <code class="literal">lockd</code> lock manager does not work
              properly; the
              <a class="link" href="server-administration.html#option_mysqld_external-locking"><code class="option">--skip-external-locking</code></a>
              option tells <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> not to use external
              locking. (This means that you cannot run two
              <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> servers on the same data
              directory and that you must be careful if you use
              <a class="link" href="programs.html#myisamchk" title="4.6.3 myisamchk — MyISAM Table-Maintenance Utility"><span class="command"><strong>myisamchk</strong></span></a>. Nevertheless, it may be
              instructive to try the option as a test.)
            </p></li><li class="listitem"><p>
              If <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> appears to be running but not
              responding, try <a class="link" href="programs.html#mysqladmin" title="4.5.2 mysqladmin — Client for Administering a MySQL Server"><span class="command"><strong>mysqladmin -u root
              processlist</strong></span></a>. Sometimes <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>
              is not hung even though it seems unresponsive. The problem
              may be that all connections are in use, or there may be
              some internal lock problem. <a class="link" href="programs.html#mysqladmin" title="4.5.2 mysqladmin — Client for Administering a MySQL Server"><span class="command"><strong>mysqladmin -u root
              processlist</strong></span></a> usually is able to make a connection
              even in these cases, and can provide useful information
              about the current number of connections and their status.
            </p></li><li class="listitem"><p>
              Run the command <a class="link" href="programs.html#mysqladmin" title="4.5.2 mysqladmin — Client for Administering a MySQL Server"><span class="command"><strong>mysqladmin -i 5 status</strong></span></a>
              or <a class="link" href="programs.html#mysqladmin" title="4.5.2 mysqladmin — Client for Administering a MySQL Server"><span class="command"><strong>mysqladmin -i 5 -r status</strong></span></a> in a
              separate window to produce statistics while running other
              queries.
            </p></li><li class="listitem"><p>
              Try the following:
</p>
<div class="orderedlist">
<ol class="orderedlist" type="1"><li class="listitem"><p>
                  Start <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> from
                  <span class="command"><strong>gdb</strong></span> (or another debugger). See
                  <a class="xref" href="extending-mysql.html#porting" title="28.5 Debugging and Porting MySQL">Section 28.5, “Debugging and Porting MySQL”</a>.
                </p></li><li class="listitem"><p>
                  Run your test scripts.
                </p></li><li class="listitem"><p>
                  Print the backtrace and the local variables at the
                  three lowest levels. In <span class="command"><strong>gdb</strong></span>, you
                  can do this with the following commands when
                  <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> has crashed inside
                  <span class="command"><strong>gdb</strong></span>:
                </p><pre data-lang="none" class="programlisting">backtrace
info local
up
info local
up
info local</pre><p>
                  With <span class="command"><strong>gdb</strong></span>, you can also examine
                  which threads exist with <code class="literal">info
                  threads</code> and switch to a specific thread with
                  <code class="literal">thread
                  <em class="replaceable"><code>N</code></em></code>, where
                  <em class="replaceable"><code>N</code></em> is the thread ID.
</p></li></ol>
</div>
</li><li class="listitem"><p>
              Try to simulate your application with a Perl script to
              force MySQL to crash or misbehave.
            </p></li><li class="listitem"><p>
              Send a normal bug report. See
              <a class="xref" href="introduction.html#bug-reports" title="1.7 How to Report Bugs or Problems">Section 1.7, “How to Report Bugs or Problems”</a>. Be even more detailed than
              usual. Because MySQL works for many people, the crash
              might result from something that exists only on your
              computer (for example, an error that is related to your
              particular system libraries).
            </p></li><li class="listitem"><p>
              If you have a problem with tables containing
              dynamic-length rows and you are using only
              <a class="link" href="data-types.html#char" title="11.3.2 The CHAR and VARCHAR Types"><code class="literal">VARCHAR</code></a> columns (not
              <a class="link" href="data-types.html#blob" title="11.3.4 The BLOB and TEXT Types"><code class="literal">BLOB</code></a> or
              <a class="link" href="data-types.html#blob" title="11.3.4 The BLOB and TEXT Types"><code class="literal">TEXT</code></a> columns), you can try
              to change all <a class="link" href="data-types.html#char" title="11.3.2 The CHAR and VARCHAR Types"><code class="literal">VARCHAR</code></a> to
              <a class="link" href="data-types.html#char" title="11.3.2 The CHAR and VARCHAR Types"><code class="literal">CHAR</code></a> with
              <a class="link" href="sql-statements.html#alter-table" title="13.1.8 ALTER TABLE Statement"><code class="literal">ALTER TABLE</code></a>. This forces
              MySQL to use fixed-size rows. Fixed-size rows take a
              little extra space, but are much more tolerant to
              corruption.
            </p><p>
              The current dynamic row code has been in use for several
              years with very few problems, but dynamic-length rows are
              by nature more prone to errors, so it may be a good idea
              to try this strategy to see whether it helps.
            </p></li><li class="listitem"><p>
              Consider the possibility of hardware faults when
              diagnosing problems. Defective hardware can be the cause
              of data corruption. Pay particular attention to your
              memory and disk subsystems when troubleshooting hardware.
</p></li></ul>
</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="full-disk"></a>B.4.3.4 How MySQL Handles a Full Disk</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183423488"></a><a class="indexterm" name="idm46734183422448"></a><p>
          This section describes how MySQL responds to disk-full errors
          (such as <span class="quote">“<span class="quote">no space left on device</span>”</span>), and to
          quota-exceeded errors (such as <span class="quote">“<span class="quote">write failed</span>”</span> or
          <span class="quote">“<span class="quote">user block limit reached</span>”</span>).
        </p><p>
          This section is relevant for writes to
          <code class="literal">MyISAM</code> tables. It also applies for writes
          to binary log files and binary log index file, except that
          references to <span class="quote">“<span class="quote">row</span>”</span> and <span class="quote">“<span class="quote">record</span>”</span>
          should be understood to mean <span class="quote">“<span class="quote">event.</span>”</span>
        </p><p>
          When a disk-full condition occurs, MySQL does the following:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              It checks once every minute to see whether there is enough
              space to write the current row. If there is enough space,
              it continues as if nothing had happened.
            </p></li><li class="listitem"><p>
              Every 10 minutes it writes an entry to the log file,
              warning about the disk-full condition.
</p></li></ul>
</div>
<p>
          To alleviate the problem, take the following actions:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              To continue, you only have to free enough disk space to
              insert all records.
            </p></li><li class="listitem"><p>
              Alternatively, to abort the thread, use
              <a class="link" href="programs.html#mysqladmin" title="4.5.2 mysqladmin — Client for Administering a MySQL Server"><span class="command"><strong>mysqladmin kill</strong></span></a>. The thread is aborted
              the next time it checks the disk (in one minute).
            </p></li><li class="listitem"><p>
              Other threads might be waiting for the table that caused
              the disk-full condition. If you have several
              <span class="quote">“<span class="quote">locked</span>”</span> threads, killing the one thread that
              is waiting on the disk-full condition enables the other
              threads to continue.
</p></li></ul>
</div>
<p>
          Exceptions to the preceding behavior are when you use
          <a class="link" href="sql-statements.html#repair-table" title="13.7.2.5 REPAIR TABLE Statement"><code class="literal">REPAIR TABLE</code></a> or
          <a class="link" href="sql-statements.html#optimize-table" title="13.7.2.4 OPTIMIZE TABLE Statement"><code class="literal">OPTIMIZE TABLE</code></a> or when the
          indexes are created in a batch after <a class="link" href="sql-statements.html#load-data" title="13.2.6 LOAD DATA Statement"><code class="literal">LOAD
          DATA</code></a> or after an <a class="link" href="sql-statements.html#alter-table" title="13.1.8 ALTER TABLE Statement"><code class="literal">ALTER
          TABLE</code></a> statement. All of these statements may create
          large temporary files that, if left to themselves, would cause
          big problems for the rest of the system. If the disk becomes
          full while MySQL is doing any of these operations, it removes
          the big temporary files and mark the table as crashed. The
          exception is that for <a class="link" href="sql-statements.html#alter-table" title="13.1.8 ALTER TABLE Statement"><code class="literal">ALTER
          TABLE</code></a>, the old table is left unchanged.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="temporary-files"></a>B.4.3.5 Where MySQL Stores Temporary Files</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183400384"></a><a class="indexterm" name="idm46734183399344"></a><a class="indexterm" name="idm46734183398256"></a><p>
          On Unix, MySQL uses the value of the <code class="literal">TMPDIR</code>
          environment variable as the path name of the directory in
          which to store temporary files. If <code class="literal">TMPDIR</code>
          is not set, MySQL uses the system default, which is usually
          <code class="filename">/tmp</code>, <code class="filename">/var/tmp</code>, or
          <code class="filename">/usr/tmp</code>.
        </p><p>
          On Windows, MySQL checks in order the values of the
          <code class="literal">TMPDIR</code>, <code class="literal">TEMP</code>, and
          <code class="literal">TMP</code> environment variables. For the first
          one found to be set, MySQL uses it and does not check those
          remaining. If none of <code class="literal">TMPDIR</code>,
          <code class="literal">TEMP</code>, or <code class="literal">TMP</code> are set,
          MySQL uses the Windows system default, which is usually
          <code class="filename">C:\windows\temp\</code>.
        </p><p>
          If the file system containing your temporary file directory is
          too small, you can use the <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>
          <a class="link" href="server-administration.html#option_mysqld_tmpdir"><code class="option">--tmpdir</code></a> option to specify a
          directory in a file system where you have enough space.
        </p><p>
          The <a class="link" href="server-administration.html#option_mysqld_tmpdir"><code class="option">--tmpdir</code></a> option can be set
          to a list of several paths that are used in round-robin
          fashion. Paths should be separated by colon characters
          (<code class="literal">:</code>) on Unix and semicolon characters
          (<code class="literal">;</code>) on Windows.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">

<div class="admon-title">
Note
</div>
<p>
            To spread the load effectively, these paths should be
            located on different <span class="emphasis"><em>physical</em></span> disks,
            not different partitions of the same disk.
</p>
</div>
<p>
          If the MySQL server is acting as a replication slave, you can
          set the <a class="link" href="replication.html#sysvar_slave_load_tmpdir"><code class="literal">slave_load_tmpdir</code></a>
          system variable to specify a separate directory for holding
          temporary files when replicating <a class="link" href="sql-statements.html#load-data" title="13.2.6 LOAD DATA Statement"><code class="literal">LOAD
          DATA</code></a> statements. This directory should be in a
          disk-based file system (not a memory-based file system) so
          that the temporary files used to replicate LOAD DATA can
          survive machine restarts. The directory also should not be one
          that is cleared by the operating system during the system
          startup process. However, replication can now continue after a
          restart if the temporary files have been removed.
        </p><p>
          MySQL arranges that temporary files are removed if
          <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> is terminated. On platforms that
          support it (such as Unix), this is done by unlinking the file
          after opening it. The disadvantage of this is that the name
          does not appear in directory listings and you do not see a big
          temporary file that fills up the file system in which the
          temporary file directory is located. (In such cases,
          <span class="command"><strong>lsof +L1</strong></span> may be helpful in identifying
          large files associated with <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>.)
        </p><p>
          When sorting (<code class="literal">ORDER BY</code> or <code class="literal">GROUP
          BY</code>), MySQL normally uses one or two temporary files.
          The maximum disk space required is determined by the following
          expression:
        </p><pre data-lang="clike" class="programlisting">(length of what is sorted + sizeof(row pointer))
* number of matched rows
* 2</pre><p>
          The row pointer size is usually four bytes, but may grow in
          the future for really big tables.
        </p><p>
          For some statements, MySQL creates temporary SQL tables that
          are not hidden and have names that begin with
          <code class="filename">#sql</code>.
        </p><p>
          Some <a class="link" href="sql-statements.html#select" title="13.2.9 SELECT Statement"><code class="literal">SELECT</code></a> queries creates
          temporary SQL tables to hold intermediate results.
        </p><p>
          DDL operations that rebuild the table and are not performed
          online using the <code class="literal">ALGORITHM=INPLACE</code>
          technique create a temporary copy of the original table in the
          same directory as the original table.
        </p><p>
          Online DDL operations may use temporary log files for
          recording concurrent DML, temporary sort files when creating
          an index, and temporary intermediate tables files when
          rebuilding the table. For more information, see
          <a class="xref" href="innodb-storage-engine.html#innodb-online-ddl-space-requirements" title="14.13.3 Online DDL Space Requirements">Section 14.13.3, “Online DDL Space Requirements”</a>.
        </p><p>
          <code class="literal">InnoDB</code> non-compressed, user-created
          temporary tables and on-disk internal temporary tables are
          created in a temporary tablespace file named
          <code class="filename">ibtmp1</code> in the MySQL data directory. For
          more information, see
          <a class="xref" href="innodb-storage-engine.html#innodb-temporary-tablespace" title="14.6.3.5 The Temporary Tablespace">Section 14.6.3.5, “The Temporary Tablespace”</a>.
        </p><p>
          See also
          <a class="xref" href="innodb-storage-engine.html#innodb-information-schema-temp-table-info" title="14.16.7 InnoDB INFORMATION_SCHEMA Temporary Table Info Table">Section 14.16.7, “InnoDB INFORMATION_SCHEMA Temporary Table Info Table”</a>.
          <a class="xref" href="innodb-storage-engine.html#innodb-orphan-temporary-tables" title="Orphan Temporary Tables">Orphan Temporary Tables</a>.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="problems-with-mysql-sock"></a>B.4.3.6 How to Protect or Change the MySQL Unix Socket File</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183356912"></a><a class="indexterm" name="idm46734183355424"></a><p>
          The default location for the Unix socket file that the server
          uses for communication with local clients is
          <code class="filename">/tmp/mysql.sock</code>. (For some distribution
          formats, the directory might be different, such as
          <code class="filename">/var/lib/mysql</code> for RPMs.)
        </p><p>
          On some versions of Unix, anyone can delete files in the
          <code class="filename">/tmp</code> directory or other similar
          directories used for temporary files. If the socket file is
          located in such a directory on your system, this might cause
          problems.
        </p><p>
          On most versions of Unix, you can protect your
          <code class="filename">/tmp</code> directory so that files can be
          deleted only by their owners or the superuser
          (<code class="literal">root</code>). To do this, set the
          <code class="literal">sticky</code> bit on the <code class="filename">/tmp</code>
          directory by logging in as <code class="literal">root</code> and using
          the following command:
        </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>chmod +t /tmp</code></strong>
</pre><p>
          You can check whether the <code class="literal">sticky</code> bit is set
          by executing <code class="literal">ls -ld /tmp</code>. If the last
          permission character is <code class="literal">t</code>, the bit is set.
        </p><a class="indexterm" name="idm46734183342064"></a><p>
          Another approach is to change the place where the server
          creates the Unix socket file. If you do this, you should also
          let client programs know the new location of the file. You can
          specify the file location in several ways:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              Specify the path in a global or local option file. For
              example, put the following lines in
              <code class="literal">/etc/my.cnf</code>:
            </p><pre data-lang="ini" class="programlisting">[mysqld]
socket=/path/to/socket

[client]
socket=/path/to/socket</pre><p>
              See <a class="xref" href="programs.html#option-files" title="4.2.2.2 Using Option Files">Section 4.2.2.2, “Using Option Files”</a>.
            </p></li><li class="listitem"><p>
              Specify a <a class="link" href="programs.html#option_general_socket"><code class="option">--socket</code></a> option
              on the command line to <a class="link" href="programs.html#mysqld-safe" title="4.3.2 mysqld_safe — MySQL Server Startup Script"><span class="command"><strong>mysqld_safe</strong></span></a> and
              when you run client programs.
            </p></li><li class="listitem"><p>
              Set the <code class="literal">MYSQL_UNIX_PORT</code> environment
              variable to the path of the Unix socket file.
            </p></li><li class="listitem"><p>
              Recompile MySQL from source to use a different default
              Unix socket file location. Define the path to the file
              with the <a class="link" href="installing.html#option_cmake_mysql_unix_addr"><code class="option">MYSQL_UNIX_ADDR</code></a>
              option when you run <span class="command"><strong>CMake</strong></span>. See
              <a class="xref" href="installing.html#source-configuration-options" title="2.9.7 MySQL Source-Configuration Options">Section 2.9.7, “MySQL Source-Configuration Options”</a>.
</p></li></ul>
</div>
<p>
          You can test whether the new socket location works by
          attempting to connect to the server with this command:
        </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>mysqladmin --socket=/path/to/socket version</code></strong>
</pre>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="timezone-problems"></a>B.4.3.7 Time Zone Problems</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183324272"></a><a class="indexterm" name="idm46734183323200"></a><a class="indexterm" name="idm46734183321712"></a><a class="indexterm" name="idm46734183320640"></a><p>
          If you have a problem with <code class="literal">SELECT NOW()</code>
          returning values in UTC and not your local time, you have to
          tell the server your current time zone. The same applies if
          <a class="link" href="functions.html#function_unix-timestamp"><code class="literal">UNIX_TIMESTAMP()</code></a> returns the
          wrong value. This should be done for the environment in which
          the server runs (for example, in
          <a class="link" href="programs.html#mysqld-safe" title="4.3.2 mysqld_safe — MySQL Server Startup Script"><span class="command"><strong>mysqld_safe</strong></span></a> or
          <a class="link" href="programs.html#mysql-server" title="4.3.3 mysql.server — MySQL Server Startup Script"><span class="command"><strong>mysql.server</strong></span></a>). See
          <a class="xref" href="programs.html#environment-variables" title="4.9 Environment Variables">Section 4.9, “Environment Variables”</a>.
        </p><p>
          You can set the time zone for the server with the
          <a class="link" href="programs.html#option_mysqld_safe_timezone"><code class="option">--timezone=<em class="replaceable"><code>timezone_name</code></em></code></a>
          option to <a class="link" href="programs.html#mysqld-safe" title="4.3.2 mysqld_safe — MySQL Server Startup Script"><span class="command"><strong>mysqld_safe</strong></span></a>. You can also set it
          by setting the <code class="literal">TZ</code> environment variable
          before you start <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>.
        </p><p>
          The permissible values for
          <a class="link" href="programs.html#option_mysqld_safe_timezone"><code class="option">--timezone</code></a> or
          <code class="literal">TZ</code> are system dependent. Consult your
          operating system documentation to see what values are
          acceptable.
</p>
</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="query-issues"></a>B.4.4 Query-Related Issues</h3>

</div>

</div>

</div>
<div class="toc">
<dl class="toc"><dt><span class="section"><a href="error-handling.html#case-sensitivity">B.4.4.1 Case Sensitivity in String Searches</a></span></dt><dt><span class="section"><a href="error-handling.html#using-date">B.4.4.2 Problems Using DATE Columns</a></span></dt><dt><span class="section"><a href="error-handling.html#problems-with-null">B.4.4.3 Problems with NULL Values</a></span></dt><dt><span class="section"><a href="error-handling.html#problems-with-alias">B.4.4.4 Problems with Column Aliases</a></span></dt><dt><span class="section"><a href="error-handling.html#nontransactional-tables">B.4.4.5 Rollback Failure for Nontransactional Tables</a></span></dt><dt><span class="section"><a href="error-handling.html#deleting-from-related-tables">B.4.4.6 Deleting Rows from Related Tables</a></span></dt><dt><span class="section"><a href="error-handling.html#no-matching-rows">B.4.4.7 Solving Problems with No Matching Rows</a></span></dt><dt><span class="section"><a href="error-handling.html#problems-with-float">B.4.4.8 Problems with Floating-Point Values</a></span></dt></dl>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="case-sensitivity"></a>B.4.4.1 Case Sensitivity in String Searches</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183303760"></a><a class="indexterm" name="idm46734183302304"></a><p>
          For nonbinary strings (<a class="link" href="data-types.html#char" title="11.3.2 The CHAR and VARCHAR Types"><code class="literal">CHAR</code></a>,
          <a class="link" href="data-types.html#char" title="11.3.2 The CHAR and VARCHAR Types"><code class="literal">VARCHAR</code></a>,
          <a class="link" href="data-types.html#blob" title="11.3.4 The BLOB and TEXT Types"><code class="literal">TEXT</code></a>), string searches use the
          collation of the comparison operands. For binary strings
          (<a class="link" href="data-types.html#binary-varbinary" title="11.3.3 The BINARY and VARBINARY Types"><code class="literal">BINARY</code></a>,
          <a class="link" href="data-types.html#binary-varbinary" title="11.3.3 The BINARY and VARBINARY Types"><code class="literal">VARBINARY</code></a>,
          <a class="link" href="data-types.html#blob" title="11.3.4 The BLOB and TEXT Types"><code class="literal">BLOB</code></a>), comparisons use the
          numeric values of the bytes in the operands; this means that
          for alphabetic characters, comparisons will be case-sensitive.
        </p><p>
          A comparison between a nonbinary string and binary string is
          treated as a comparison of binary strings.
        </p><p>
          Simple comparison operations (<code class="literal">&gt;=, &gt;, =, &lt;,
          &lt;=</code>, sorting, and grouping) are based on each
          character's <span class="quote">“<span class="quote">sort value.</span>”</span> Characters with the
          same sort value are treated as the same character. For
          example, if <code class="literal">e</code> and
          <code class="literal">é</code> have the same sort value in a
          given collation, they compare as equal.
        </p><p>
          The default character set and collation are
          <code class="literal">latin1</code> and
          <code class="literal">latin1_swedish_ci</code>, so nonbinary string
          comparisons are case-insensitive by default. This means that
          if you search with
          <code class="literal"><em class="replaceable"><code>col_name</code></em> LIKE
          'a%'</code>, you get all column values that start with
          <code class="literal">A</code> or <code class="literal">a</code>. To make this
          search case-sensitive, make sure that one of the operands has
          a case-sensitive or binary collation. For example, if you are
          comparing a column and a string that both have the
          <code class="literal">latin1</code> character set, you can use the
          <code class="literal">COLLATE</code> operator to cause either operand to
          have the <code class="literal">latin1_general_cs</code> or
          <code class="literal">latin1_bin</code> collation:
        </p><pre data-lang="sql" class="programlisting"><em class="replaceable"><code>col_name</code></em> COLLATE latin1_general_cs LIKE 'a%'
<em class="replaceable"><code>col_name</code></em> LIKE 'a%' COLLATE latin1_general_cs
<em class="replaceable"><code>col_name</code></em> COLLATE latin1_bin LIKE 'a%'
<em class="replaceable"><code>col_name</code></em> LIKE 'a%' COLLATE latin1_bin
</pre><p>
          If you want a column always to be treated in case-sensitive
          fashion, declare it with a case-sensitive or binary collation.
          See <a class="xref" href="sql-statements.html#create-table" title="13.1.18 CREATE TABLE Statement">Section 13.1.18, “CREATE TABLE Statement”</a>.
        </p><p>
          To cause a case-sensitive comparison of nonbinary strings to
          be case-insensitive, use <code class="literal">COLLATE</code> to name a
          case-insensitive collation. The strings in the following
          example normally are case-sensitive, but
          <code class="literal">COLLATE</code> changes the comparison to be
          case-insensitive:
        </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>SET @s1 = 'MySQL' COLLATE latin1_bin,</code></strong>
    -&gt; <strong class="userinput"><code>    @s2 = 'mysql' COLLATE latin1_bin;</code></strong>
mysql&gt; <strong class="userinput"><code>SELECT @s1 = @s2;</code></strong>
+-----------+
| @s1 = @s2 |
+-----------+
|         0 |
+-----------+
mysql&gt; <strong class="userinput"><code>SELECT @s1 COLLATE latin1_swedish_ci = @s2;</code></strong>
+-------------------------------------+
| @s1 COLLATE latin1_swedish_ci = @s2 |
+-------------------------------------+
|                                   1 |
+-------------------------------------+
</pre><p>
          A binary string is case-sensitive in comparisons. To compare
          the string as case-insensitive, convert it to a nonbinary
          string and use <code class="literal">COLLATE</code> to name a
          case-insensitive collation:
        </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>SET @s = BINARY 'MySQL';</code></strong>
mysql&gt; <strong class="userinput"><code>SELECT @s = 'mysql';</code></strong>
+--------------+
| @s = 'mysql' |
+--------------+
|            0 |
+--------------+
mysql&gt; <strong class="userinput"><code>SELECT CONVERT(@s USING latin1) COLLATE latin1_swedish_ci = 'mysql';</code></strong>
+--------------------------------------------------------------+
| CONVERT(@s USING latin1) COLLATE latin1_swedish_ci = 'mysql' |
+--------------------------------------------------------------+
|                                                            1 |
+--------------------------------------------------------------+
</pre><p>
          To determine whether a value will compare as a nonbinary or
          binary string, use the
          <a class="link" href="functions.html#function_collation"><code class="literal">COLLATION()</code></a> function. This
          example shows that <a class="link" href="functions.html#function_version"><code class="literal">VERSION()</code></a>
          returns a string that has a case-insensitive collation, so
          comparisons are case-insensitive:
        </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>SELECT COLLATION(VERSION());</code></strong>
+----------------------+
| COLLATION(VERSION()) |
+----------------------+
| utf8_general_ci      |
+----------------------+
</pre><p>
          For binary strings, the collation value is
          <code class="literal">binary</code>, so comparisons will be
          case-sensitive. One context in which you will see
          <code class="literal">binary</code> is for compression functions, which
          return binary strings as a general rule: string:
        </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>SELECT COLLATION(COMPRESS('x'));</code></strong>
+--------------------------+
| COLLATION(COMPRESS('x')) |
+--------------------------+
| binary                   |
+--------------------------+
</pre><p>
          To check the sort value of a string, the
          <a class="link" href="functions.html#function_weight-string"><code class="literal">WEIGHT_STRING()</code></a> may be helpful.
          See <a class="xref" href="functions.html#string-functions" title="12.7 String Functions and Operators">Section 12.7, “String Functions and Operators”</a>.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="using-date"></a>B.4.4.2 Problems Using DATE Columns</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183253712"></a><a class="indexterm" name="idm46734183252672"></a><a class="indexterm" name="idm46734183251184"></a><p>
          The format of a <a class="link" href="data-types.html#datetime" title="11.2.2 The DATE, DATETIME, and TIMESTAMP Types"><code class="literal">DATE</code></a> value is
          <code class="literal">'<em class="replaceable"><code>YYYY-MM-DD</code></em>'</code>.
          According to standard SQL, no other format is permitted. You
          should use this format in
          <a class="link" href="sql-statements.html#update" title="13.2.11 UPDATE Statement"><code class="literal">UPDATE</code></a> expressions and in the
          <code class="literal">WHERE</code> clause of
          <a class="link" href="sql-statements.html#select" title="13.2.9 SELECT Statement"><code class="literal">SELECT</code></a> statements. For example:
        </p><pre data-lang="sql" class="programlisting">SELECT * FROM t1 WHERE date &gt;= '2003-05-05';</pre><p>
          As a convenience, MySQL automatically converts a date to a
          number if the date is used in numeric context and vice versa.
          MySQL also permits a <span class="quote">“<span class="quote">relaxed</span>”</span> string format when
          updating and in a <code class="literal">WHERE</code> clause that
          compares a date to a <a class="link" href="data-types.html#datetime" title="11.2.2 The DATE, DATETIME, and TIMESTAMP Types"><code class="literal">DATE</code></a>,
          <a class="link" href="data-types.html#datetime" title="11.2.2 The DATE, DATETIME, and TIMESTAMP Types"><code class="literal">DATETIME</code></a>, or
          <a class="link" href="data-types.html#datetime" title="11.2.2 The DATE, DATETIME, and TIMESTAMP Types"><code class="literal">TIMESTAMP</code></a> column.
          <span class="quote">“<span class="quote">Relaxed</span>”</span> format means that any punctuation
          character may be used as the separator between parts. For
          example, <code class="literal">'2004-08-15'</code> and
          <code class="literal">'2004#08#15'</code> are equivalent. MySQL can also
          convert a string containing no separators (such as
          <code class="literal">'20040815'</code>), provided it makes sense as a
          date.
        </p><p>
          When you compare a <a class="link" href="data-types.html#datetime" title="11.2.2 The DATE, DATETIME, and TIMESTAMP Types"><code class="literal">DATE</code></a>,
          <a class="link" href="data-types.html#time" title="11.2.3 The TIME Type"><code class="literal">TIME</code></a>,
          <a class="link" href="data-types.html#datetime" title="11.2.2 The DATE, DATETIME, and TIMESTAMP Types"><code class="literal">DATETIME</code></a>, or
          <a class="link" href="data-types.html#datetime" title="11.2.2 The DATE, DATETIME, and TIMESTAMP Types"><code class="literal">TIMESTAMP</code></a> to a constant string
          with the <code class="literal">&lt;</code>, <code class="literal">&lt;=</code>,
          <code class="literal">=</code>, <code class="literal">&gt;=</code>,
          <code class="literal">&gt;</code>, or <code class="literal">BETWEEN</code>
          operators, MySQL normally converts the string to an internal
          long integer for faster comparison (and also for a bit more
          <span class="quote">“<span class="quote">relaxed</span>”</span> string checking). However, this
          conversion is subject to the following exceptions:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              When you compare two columns
            </p></li><li class="listitem"><p>
              When you compare a <a class="link" href="data-types.html#datetime" title="11.2.2 The DATE, DATETIME, and TIMESTAMP Types"><code class="literal">DATE</code></a>,
              <a class="link" href="data-types.html#time" title="11.2.3 The TIME Type"><code class="literal">TIME</code></a>,
              <a class="link" href="data-types.html#datetime" title="11.2.2 The DATE, DATETIME, and TIMESTAMP Types"><code class="literal">DATETIME</code></a>, or
              <a class="link" href="data-types.html#datetime" title="11.2.2 The DATE, DATETIME, and TIMESTAMP Types"><code class="literal">TIMESTAMP</code></a> column to an
              expression
            </p></li><li class="listitem"><p>
              When you use any comparison method other than those just
              listed, such as <code class="literal">IN</code> or
              <a class="link" href="functions.html#function_strcmp"><code class="literal">STRCMP()</code></a>.
</p></li></ul>
</div>
<p>
          For those exceptions, the comparison is done by converting the
          objects to strings and performing a string comparison.
        </p><p>
          To be on the safe side, assume that strings are compared as
          strings and use the appropriate string functions if you want
          to compare a temporal value to a string.
        </p><p>
          The special <span class="quote">“<span class="quote">zero</span>”</span> date
          <code class="literal">'0000-00-00'</code> can be stored and retrieved as
          <code class="literal">'0000-00-00'.</code> When a
          <code class="literal">'0000-00-00'</code> date is used through
          Connector/ODBC, it is automatically converted to
          <code class="literal">NULL</code> because ODBC cannot handle that kind
          of date.
        </p><p>
          Because MySQL performs the conversions just described, the
          following statements work (assume that
          <code class="literal">idate</code> is a
          <a class="link" href="data-types.html#datetime" title="11.2.2 The DATE, DATETIME, and TIMESTAMP Types"><code class="literal">DATE</code></a> column):
        </p><pre data-lang="sql" class="programlisting">INSERT INTO t1 (idate) VALUES (19970505);
INSERT INTO t1 (idate) VALUES ('19970505');
INSERT INTO t1 (idate) VALUES ('97-05-05');
INSERT INTO t1 (idate) VALUES ('1997.05.05');
INSERT INTO t1 (idate) VALUES ('1997 05 05');
INSERT INTO t1 (idate) VALUES ('0000-00-00');

SELECT idate FROM t1 WHERE idate &gt;= '1997-05-05';
SELECT idate FROM t1 WHERE idate &gt;= 19970505;
SELECT MOD(idate,100) FROM t1 WHERE idate &gt;= 19970505;
SELECT idate FROM t1 WHERE idate &gt;= '19970505';</pre><p>
          However, the following statement does not work:
        </p><pre data-lang="sql" class="programlisting">SELECT idate FROM t1 WHERE STRCMP(idate,'20030505')=0;</pre><p>
          <a class="link" href="functions.html#function_strcmp"><code class="literal">STRCMP()</code></a> is a string function,
          so it converts <code class="literal">idate</code> to a string in
          <code class="literal">'<em class="replaceable"><code>YYYY-MM-DD</code></em>'</code>
          format and performs a string comparison. It does not convert
          <code class="literal">'20030505'</code> to the date
          <code class="literal">'2003-05-05'</code> and perform a date comparison.
        </p><p>
          If you enable the
          <a class="link" href="server-administration.html#sqlmode_allow_invalid_dates"><code class="literal">ALLOW_INVALID_DATES</code></a> SQL
          mode, MySQL permits you to store dates that are given only
          limited checking: MySQL requires only that the day is in the
          range from 1 to 31 and the month is in the range from 1 to 12.
          This makes MySQL very convenient for Web applications where
          you obtain year, month, and day in three different fields and
          you want to store exactly what the user inserted (without date
          validation).
        </p><p>
          MySQL permits you to store dates where the day or month and
          day are zero. This is convenient if you want to store a
          birthdate in a <a class="link" href="data-types.html#datetime" title="11.2.2 The DATE, DATETIME, and TIMESTAMP Types"><code class="literal">DATE</code></a> column and
          you know only part of the date. To disallow zero month or day
          parts in dates, enable the
          <a class="link" href="server-administration.html#sqlmode_no_zero_in_date"><code class="literal">NO_ZERO_IN_DATE</code></a> mode.
        </p><p>
          MySQL permits you to store a <span class="quote">“<span class="quote">zero</span>”</span> value of
          <code class="literal">'0000-00-00'</code> as a <span class="quote">“<span class="quote">dummy
          date.</span>”</span> This is in some cases more convenient than using
          <code class="literal">NULL</code> values. If a date to be stored in a
          <a class="link" href="data-types.html#datetime" title="11.2.2 The DATE, DATETIME, and TIMESTAMP Types"><code class="literal">DATE</code></a> column cannot be converted
          to any reasonable value, MySQL stores
          <code class="literal">'0000-00-00'</code>. To disallow
          <code class="literal">'0000-00-00'</code>, enable the
          <a class="link" href="server-administration.html#sqlmode_no_zero_date"><code class="literal">NO_ZERO_DATE</code></a> mode.
        </p><p>
          To have MySQL check all dates and accept only legal dates
          (unless overridden by <code class="literal">IGNORE</code>), set the
          <a class="link" href="server-administration.html#sysvar_sql_mode"><code class="literal">sql_mode</code></a> system variable to
          <code class="literal">"NO_ZERO_IN_DATE,NO_ZERO_DATE"</code>.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="problems-with-null"></a>B.4.4.3 Problems with NULL Values</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183182144"></a><a class="indexterm" name="idm46734183180688"></a><p>
          The concept of the <code class="literal">NULL</code> value is a common
          source of confusion for newcomers to SQL, who often think that
          <code class="literal">NULL</code> is the same thing as an empty string
          <code class="literal">''</code>. This is not the case. For example, the
          following statements are completely different:
        </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>INSERT INTO my_table (phone) VALUES (NULL);</code></strong>
mysql&gt; <strong class="userinput"><code>INSERT INTO my_table (phone) VALUES ('');</code></strong>
</pre><p>
          Both statements insert a value into the
          <code class="literal">phone</code> column, but the first inserts a
          <code class="literal">NULL</code> value and the second inserts an empty
          string. The meaning of the first can be regarded as
          <span class="quote">“<span class="quote">phone number is not known</span>”</span> and the meaning of
          the second can be regarded as <span class="quote">“<span class="quote">the person is known to
          have no phone, and thus no phone number.</span>”</span>
        </p><p>
          To help with <code class="literal">NULL</code> handling, you can use the
          <a class="link" href="functions.html#operator_is-null"><code class="literal">IS NULL</code></a> and <a class="link" href="functions.html#operator_is-not-null"><code class="literal">IS
          NOT NULL</code></a> operators and the
          <a class="link" href="functions.html#function_ifnull"><code class="literal">IFNULL()</code></a> function.
        </p><p>
          In SQL, the <code class="literal">NULL</code> value is never true in
          comparison to any other value, even <code class="literal">NULL</code>.
          An expression that contains <code class="literal">NULL</code> always
          produces a <code class="literal">NULL</code> value unless otherwise
          indicated in the documentation for the operators and functions
          involved in the expression. All columns in the following
          example return <code class="literal">NULL</code>:
        </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>SELECT NULL, 1+NULL, CONCAT('Invisible',NULL);</code></strong>
</pre><p>
          To search for column values that are <code class="literal">NULL</code>,
          you cannot use an <code class="literal">expr = NULL</code> test. The
          following statement returns no rows, because <code class="literal">expr =
          NULL</code> is never true for any expression:
        </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>SELECT * FROM my_table WHERE phone = NULL;</code></strong>
</pre><p>
          To look for <code class="literal">NULL</code> values, you must use the
          <a class="link" href="functions.html#operator_is-null"><code class="literal">IS NULL</code></a> test. The following
          statements show how to find the <code class="literal">NULL</code> phone
          number and the empty phone number:
        </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>SELECT * FROM my_table WHERE phone IS NULL;</code></strong>
mysql&gt; <strong class="userinput"><code>SELECT * FROM my_table WHERE phone = '';</code></strong>
</pre><p>
          See <a class="xref" href="tutorial.html#working-with-null" title="3.3.4.6 Working with NULL Values">Section 3.3.4.6, “Working with NULL Values”</a>, for additional
          information and examples.
        </p><p>
          You can add an index on a column that can have
          <code class="literal">NULL</code> values if you are using the
          <code class="literal">MyISAM</code>, <code class="literal">InnoDB</code>, or
          <code class="literal">MEMORY</code> storage engine. Otherwise, you must
          declare an indexed column <code class="literal">NOT NULL</code>, and you
          cannot insert <code class="literal">NULL</code> into the column.
        </p><a class="indexterm" name="idm46734183144656"></a><p>
          When reading data with <a class="link" href="sql-statements.html#load-data" title="13.2.6 LOAD DATA Statement"><code class="literal">LOAD
          DATA</code></a>, empty or missing columns are updated with
          <code class="literal">''</code>. To load a <code class="literal">NULL</code> value
          into a column, use <code class="literal">\N</code> in the data file. The
          literal word <code class="literal">NULL</code> may also be used under
          some circumstances. See <a class="xref" href="sql-statements.html#load-data" title="13.2.6 LOAD DATA Statement">Section 13.2.6, “LOAD DATA Statement”</a>.
        </p><p>
          When using <code class="literal">DISTINCT</code>, <code class="literal">GROUP
          BY</code>, or <code class="literal">ORDER BY</code>, all
          <code class="literal">NULL</code> values are regarded as equal.
        </p><p>
          When using <code class="literal">ORDER BY</code>,
          <code class="literal">NULL</code> values are presented first, or last if
          you specify <code class="literal">DESC</code> to sort in descending
          order.
        </p><p>
          Aggregate (summary) functions such as
          <a class="link" href="functions.html#function_count"><code class="literal">COUNT()</code></a>,
          <a class="link" href="functions.html#function_min"><code class="literal">MIN()</code></a>, and
          <a class="link" href="functions.html#function_sum"><code class="literal">SUM()</code></a> ignore
          <code class="literal">NULL</code> values. The exception to this is
          <a class="link" href="functions.html#function_count"><code class="literal">COUNT(*)</code></a>, which counts rows and
          not individual column values. For example, the following
          statement produces two counts. The first is a count of the
          number of rows in the table, and the second is a count of the
          number of non-<code class="literal">NULL</code> values in the
          <code class="literal">age</code> column:
        </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>SELECT COUNT(*), COUNT(age) FROM person;</code></strong>
</pre><a class="indexterm" name="idm46734183122912"></a><a class="indexterm" name="idm46734183121424"></a><a class="indexterm" name="idm46734183119936"></a><a class="indexterm" name="idm46734183118448"></a><p>
          For some data types, MySQL handles <code class="literal">NULL</code>
          values specially. If you insert <code class="literal">NULL</code> into a
          <a class="link" href="data-types.html#datetime" title="11.2.2 The DATE, DATETIME, and TIMESTAMP Types"><code class="literal">TIMESTAMP</code></a> column, the current
          date and time is inserted. If you insert
          <code class="literal">NULL</code> into an integer or floating-point
          column that has the <code class="literal">AUTO_INCREMENT</code>
          attribute, the next number in the sequence is inserted.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="problems-with-alias"></a>B.4.4.4 Problems with Column Aliases</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183110896"></a><a class="indexterm" name="idm46734183109440"></a><a class="indexterm" name="idm46734183107952"></a><p>
          An alias can be used in a query select list to give a column a
          different name. You can use the alias in <code class="literal">GROUP
          BY</code>, <code class="literal">ORDER BY</code>, or
          <code class="literal">HAVING</code> clauses to refer to the column:
        </p><pre data-lang="sql" class="programlisting">SELECT SQRT(a*b) AS root FROM <em class="replaceable"><code>tbl_name</code></em>
  GROUP BY root HAVING root &gt; 0;
SELECT id, COUNT(*) AS cnt FROM <em class="replaceable"><code>tbl_name</code></em>
  GROUP BY id HAVING cnt &gt; 0;
SELECT id AS 'Customer identity' FROM <em class="replaceable"><code>tbl_name</code></em>;
</pre><p>
          Standard SQL disallows references to column aliases in a
          <code class="literal">WHERE</code> clause. This restriction is imposed
          because when the <code class="literal">WHERE</code> clause is evaluated,
          the column value may not yet have been determined. For
          example, the following query is illegal:
        </p><pre data-lang="sql" class="programlisting">SELECT id, COUNT(*) AS cnt FROM <em class="replaceable"><code>tbl_name</code></em>
  WHERE cnt &gt; 0 GROUP BY id;
</pre><p>
          The <code class="literal">WHERE</code> clause determines which rows
          should be included in the <code class="literal">GROUP BY</code> clause,
          but it refers to the alias of a column value that is not known
          until after the rows have been selected, and grouped by the
          <code class="literal">GROUP BY</code>.
        </p><p>
          In the select list of a query, a quoted column alias can be
          specified using identifier or string quoting characters:
        </p><pre data-lang="sql" class="programlisting">SELECT 1 AS `one`, 2 AS 'two';</pre><p>
          Elsewhere in the statement, quoted references to the alias
          must use identifier quoting or the reference is treated as a
          string literal. For example, this statement groups by the
          values in column <code class="literal">id</code>, referenced using the
          alias <code class="literal">`a`</code>:
        </p><pre data-lang="sql" class="programlisting">SELECT id AS 'a', COUNT(*) AS cnt FROM <em class="replaceable"><code>tbl_name</code></em>
  GROUP BY `a`;
</pre><p>
          But this statement groups by the literal string
          <code class="literal">'a'</code> and will not work as expected:
        </p><pre data-lang="sql" class="programlisting">SELECT id AS 'a', COUNT(*) AS cnt FROM <em class="replaceable"><code>tbl_name</code></em>
  GROUP BY 'a';
</pre>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="nontransactional-tables"></a>B.4.4.5 Rollback Failure for Nontransactional Tables</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183085952"></a><p>
          If you receive the following message when trying to perform a
          <a class="link" href="sql-statements.html#commit" title="13.3.1 START TRANSACTION, COMMIT, and ROLLBACK Statements"><code class="literal">ROLLBACK</code></a>, it
          means that one or more of the tables you used in the
          transaction do not support transactions:
        </p><pre data-lang="none" class="programlisting">Warning: Some non-transactional changed tables couldn't be rolled back</pre><p>
          These nontransactional tables are not affected by the
          <a class="link" href="sql-statements.html#commit" title="13.3.1 START TRANSACTION, COMMIT, and ROLLBACK Statements"><code class="literal">ROLLBACK</code></a>
          statement.
        </p><p>
          If you were not deliberately mixing transactional and
          nontransactional tables within the transaction, the most
          likely cause for this message is that a table you thought was
          transactional actually is not. This can happen if you try to
          create a table using a transactional storage engine that is
          not supported by your <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> server (or
          that was disabled with a startup option). If
          <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> does not support a storage engine,
          it instead creates the table as a <code class="literal">MyISAM</code>
          table, which is nontransactional.
        </p><p>
          You can check the storage engine for a table by using either
          of these statements:
        </p><pre data-lang="sql" class="programlisting">SHOW TABLE STATUS LIKE '<em class="replaceable"><code>tbl_name</code></em>';
SHOW CREATE TABLE <em class="replaceable"><code>tbl_name</code></em>;
</pre><p>
          See <a class="xref" href="sql-statements.html#show-table-status" title="13.7.5.36 SHOW TABLE STATUS Statement">Section 13.7.5.36, “SHOW TABLE STATUS Statement”</a>, and
          <a class="xref" href="sql-statements.html#show-create-table" title="13.7.5.10 SHOW CREATE TABLE Statement">Section 13.7.5.10, “SHOW CREATE TABLE Statement”</a>.
        </p><p>
          To check which storage engines your <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a>
          server supports, use this statement:
        </p><pre data-lang="sql" class="programlisting">SHOW ENGINES;</pre><p>
          See <a class="xref" href="sql-statements.html#show-engines" title="13.7.5.16 SHOW ENGINES Statement">Section 13.7.5.16, “SHOW ENGINES Statement”</a> for full details.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="deleting-from-related-tables"></a>B.4.4.6 Deleting Rows from Related Tables</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183067024"></a><a class="indexterm" name="idm46734183065568"></a><a class="indexterm" name="idm46734183064080"></a><p>
          If the total length of the
          <a class="link" href="sql-statements.html#delete" title="13.2.2 DELETE Statement"><code class="literal">DELETE</code></a> statement for
          <code class="literal">related_table</code> is more than 1MB (the default
          value of the
          <a class="link" href="server-administration.html#sysvar_max_allowed_packet"><code class="literal">max_allowed_packet</code></a> system
          variable), you should split it into smaller parts and execute
          multiple <a class="link" href="sql-statements.html#delete" title="13.2.2 DELETE Statement"><code class="literal">DELETE</code></a> statements. You
          probably get the fastest <a class="link" href="sql-statements.html#delete" title="13.2.2 DELETE Statement"><code class="literal">DELETE</code></a>
          by specifying only 100 to 1,000
          <code class="literal">related_column</code> values per statement if the
          <code class="literal">related_column</code> is indexed. If the
          <code class="literal">related_column</code> isn't indexed, the speed is
          independent of the number of arguments in the
          <code class="literal">IN</code> clause.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="no-matching-rows"></a>B.4.4.7 Solving Problems with No Matching Rows</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734183052080"></a><a class="indexterm" name="idm46734183051040"></a><p>
          If you have a complicated query that uses many tables but that
          returns no rows, you should use the following procedure to
          find out what is wrong:
</p>
<div class="orderedlist">
<ol class="orderedlist" type="1"><li class="listitem"><p>
              Test the query with <a class="link" href="sql-statements.html#explain" title="13.8.2 EXPLAIN Statement"><code class="literal">EXPLAIN</code></a>
              to check whether you can find something that is obviously
              wrong. See <a class="xref" href="sql-statements.html#explain" title="13.8.2 EXPLAIN Statement">Section 13.8.2, “EXPLAIN Statement”</a>.
            </p></li><li class="listitem"><p>
              Select only those columns that are used in the
              <code class="literal">WHERE</code> clause.
            </p></li><li class="listitem"><p>
              Remove one table at a time from the query until it returns
              some rows. If the tables are large, it is a good idea to
              use <code class="literal">LIMIT 10</code> with the query.
            </p></li><li class="listitem"><p>
              Issue a <a class="link" href="sql-statements.html#select" title="13.2.9 SELECT Statement"><code class="literal">SELECT</code></a> for the
              column that should have matched a row against the table
              that was last removed from the query.
            </p></li><li class="listitem"><p>
              If you are comparing <a class="link" href="data-types.html#floating-point-types" title="11.1.4 Floating-Point Types (Approximate Value) - FLOAT, DOUBLE"><code class="literal">FLOAT</code></a>
              or <a class="link" href="data-types.html#floating-point-types" title="11.1.4 Floating-Point Types (Approximate Value) - FLOAT, DOUBLE"><code class="literal">DOUBLE</code></a> columns with
              numbers that have decimals, you cannot use equality
              (<code class="literal">=</code>) comparisons. This problem is common
              in most computer languages because not all floating-point
              values can be stored with exact precision. In some cases,
              changing the <a class="link" href="data-types.html#floating-point-types" title="11.1.4 Floating-Point Types (Approximate Value) - FLOAT, DOUBLE"><code class="literal">FLOAT</code></a> to a
              <a class="link" href="data-types.html#floating-point-types" title="11.1.4 Floating-Point Types (Approximate Value) - FLOAT, DOUBLE"><code class="literal">DOUBLE</code></a> fixes this. See
              <a class="xref" href="error-handling.html#problems-with-float" title="B.4.4.8 Problems with Floating-Point Values">Section B.4.4.8, “Problems with Floating-Point Values”</a>.
            </p></li><li class="listitem"><p>
              If you still cannot figure out what is wrong, create a
              minimal test that can be run with <code class="literal">mysql test &lt;
              query.sql</code> that shows your problems. You can
              create a test file by dumping the tables with
              <a class="link" href="programs.html#mysqldump" title="4.5.4 mysqldump — A Database Backup Program"><span class="command"><strong>mysqldump --quick db_name
              <em class="replaceable"><code>tbl_name_1</code></em> ...
              <em class="replaceable"><code>tbl_name_n</code></em> &gt;
              query.sql</strong></span></a>. Open the file in an editor, remove
              some insert lines (if there are more than needed to
              demonstrate the problem), and add your
              <a class="link" href="sql-statements.html#select" title="13.2.9 SELECT Statement"><code class="literal">SELECT</code></a> statement at the end
              of the file.
            </p><p>
              Verify that the test file demonstrates the problem by
              executing these commands:
            </p><pre data-lang="terminal" class="programlisting">shell&gt; <strong class="userinput"><code>mysqladmin create test2</code></strong>
shell&gt; <strong class="userinput"><code>mysql test2 &lt; query.sql</code></strong>
</pre><p>
              Attach the test file to a bug report, which you can file
              using the instructions in <a class="xref" href="introduction.html#bug-reports" title="1.7 How to Report Bugs or Problems">Section 1.7, “How to Report Bugs or Problems”</a>.
</p></li></ol>
</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="problems-with-float"></a>B.4.4.8 Problems with Floating-Point Values</h4>

</div>

</div>

</div>
<p>
          Floating-point numbers sometimes cause confusion because they
          are approximate and not stored as exact values. A
          floating-point value as written in an SQL statement may not be
          the same as the value represented internally. Attempts to
          treat floating-point values as exact in comparisons may lead
          to problems. They are also subject to platform or
          implementation dependencies. The
          <a class="link" href="data-types.html#floating-point-types" title="11.1.4 Floating-Point Types (Approximate Value) - FLOAT, DOUBLE"><code class="literal">FLOAT</code></a> and
          <a class="link" href="data-types.html#floating-point-types" title="11.1.4 Floating-Point Types (Approximate Value) - FLOAT, DOUBLE"><code class="literal">DOUBLE</code></a> data types are subject
          to these issues. For <a class="link" href="data-types.html#fixed-point-types" title="11.1.3 Fixed-Point Types (Exact Value) - DECIMAL, NUMERIC"><code class="literal">DECIMAL</code></a>
          columns, MySQL performs operations with a precision of 65
          decimal digits, which should solve most common inaccuracy
          problems.
        </p><p>
          The following example uses
          <a class="link" href="data-types.html#floating-point-types" title="11.1.4 Floating-Point Types (Approximate Value) - FLOAT, DOUBLE"><code class="literal">DOUBLE</code></a> to demonstrate how
          calculations that are done using floating-point operations are
          subject to floating-point error.
        </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>CREATE TABLE t1 (i INT, d1 DOUBLE, d2 DOUBLE);</code></strong>
mysql&gt; <strong class="userinput"><code>INSERT INTO t1 VALUES (1, 101.40, 21.40), (1, -80.00, 0.00),</code></strong>
    -&gt; <strong class="userinput"><code>(2, 0.00, 0.00), (2, -13.20, 0.00), (2, 59.60, 46.40),</code></strong>
    -&gt; <strong class="userinput"><code>(2, 30.40, 30.40), (3, 37.00, 7.40), (3, -29.60, 0.00),</code></strong>
    -&gt; <strong class="userinput"><code>(4, 60.00, 15.40), (4, -10.60, 0.00), (4, -34.00, 0.00),</code></strong>
    -&gt; <strong class="userinput"><code>(5, 33.00, 0.00), (5, -25.80, 0.00), (5, 0.00, 7.20),</code></strong>
    -&gt; <strong class="userinput"><code>(6, 0.00, 0.00), (6, -51.40, 0.00);</code></strong>

mysql&gt; <strong class="userinput"><code>SELECT i, SUM(d1) AS a, SUM(d2) AS b</code></strong>
    -&gt; <strong class="userinput"><code>FROM t1 GROUP BY i HAVING a &lt;&gt; b;</code></strong>

+------+-------+------+
| i    | a     | b    |
+------+-------+------+
|    1 |  21.4 | 21.4 |
|    2 |  76.8 | 76.8 |
|    3 |   7.4 |  7.4 |
|    4 |  15.4 | 15.4 |
|    5 |   7.2 |  7.2 |
|    6 | -51.4 |    0 |
+------+-------+------+
</pre><p>
          The result is correct. Although the first five records look
          like they should not satisfy the comparison (the values of
          <code class="literal">a</code> and <code class="literal">b</code> do not appear to
          be different), they may do so because the difference between
          the numbers shows up around the tenth decimal or so, depending
          on factors such as computer architecture or the compiler
          version or optimization level. For example, different CPUs may
          evaluate floating-point numbers differently.
        </p><p>
          If columns <code class="literal">d1</code> and <code class="literal">d2</code> had
          been defined as <a class="link" href="data-types.html#fixed-point-types" title="11.1.3 Fixed-Point Types (Exact Value) - DECIMAL, NUMERIC"><code class="literal">DECIMAL</code></a> rather
          than <a class="link" href="data-types.html#floating-point-types" title="11.1.4 Floating-Point Types (Approximate Value) - FLOAT, DOUBLE"><code class="literal">DOUBLE</code></a>, the result of the
          <a class="link" href="sql-statements.html#select" title="13.2.9 SELECT Statement"><code class="literal">SELECT</code></a> query would have
          contained only one row—the last one shown above.
        </p><p>
          The correct way to do floating-point number comparison is to
          first decide on an acceptable tolerance for differences
          between the numbers and then do the comparison against the
          tolerance value. For example, if we agree that floating-point
          numbers should be regarded the same if they are same within a
          precision of one in ten thousand (0.0001), the comparison
          should be written to find differences larger than the
          tolerance value:
        </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>SELECT i, SUM(d1) AS a, SUM(d2) AS b FROM t1</code></strong>
    -&gt; <strong class="userinput"><code>GROUP BY i HAVING ABS(a - b) &gt; 0.0001;</code></strong>
+------+-------+------+
| i    | a     | b    |
+------+-------+------+
|    6 | -51.4 |    0 |
+------+-------+------+
1 row in set (0.00 sec)
</pre><p>
          Conversely, to get rows where the numbers are the same, the
          test should find differences within the tolerance value:
        </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>SELECT i, SUM(d1) AS a, SUM(d2) AS b FROM t1</code></strong>
    -&gt; <strong class="userinput"><code>GROUP BY i HAVING ABS(a - b) &lt;= 0.0001;</code></strong>
+------+------+------+
| i    | a    | b    |
+------+------+------+
|    1 | 21.4 | 21.4 |
|    2 | 76.8 | 76.8 |
|    3 |  7.4 |  7.4 |
|    4 | 15.4 | 15.4 |
|    5 |  7.2 |  7.2 |
+------+------+------+
5 rows in set (0.03 sec)
</pre><p>
          Floating-point values are subject to platform or
          implementation dependencies. Suppose that you execute the
          following statements:
        </p><pre data-lang="sql" class="programlisting">CREATE TABLE t1(c1 FLOAT(53,0), c2 FLOAT(53,0));
INSERT INTO t1 VALUES('1e+52','-1e+52');
SELECT * FROM t1;</pre><p>
          On some platforms, the <code class="literal">SELECT</code> statement
          returns <code class="literal">inf</code> and <code class="literal">-inf</code>. On
          others, it returns <code class="literal">0</code> and
          <code class="literal">-0</code>.
        </p><p>
          An implication of the preceding issues is that if you attempt
          to create a replication slave by dumping table contents with
          <a class="link" href="programs.html#mysqldump" title="4.5.4 mysqldump — A Database Backup Program"><span class="command"><strong>mysqldump</strong></span></a> on the master and reloading the
          dump file into the slave, tables containing floating-point
          columns might differ between the two hosts.
</p>
</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="optimizer-issues"></a>B.4.5 Optimizer-Related Issues</h3>

</div>

</div>

</div>
<p>
        MySQL uses a cost-based optimizer to determine the best way to
        resolve a query. In many cases, MySQL can calculate the best
        possible query plan, but sometimes MySQL does not have enough
        information about the data at hand and has to make
        <span class="quote">“<span class="quote">educated</span>”</span> guesses about the data.
      </p><p>
        For the cases when MySQL does not do the "right" thing, tools
        that you have available to help MySQL are:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
            Use the <a class="link" href="sql-statements.html#explain" title="13.8.2 EXPLAIN Statement"><code class="literal">EXPLAIN</code></a> statement to
            get information about how MySQL processes a query. To use
            it, just add the keyword
            <a class="link" href="sql-statements.html#explain" title="13.8.2 EXPLAIN Statement"><code class="literal">EXPLAIN</code></a> to the front of your
            <a class="link" href="sql-statements.html#select" title="13.2.9 SELECT Statement"><code class="literal">SELECT</code></a> statement:
          </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>EXPLAIN SELECT * FROM t1, t2 WHERE t1.i = t2.i;</code></strong>
</pre><p>
            <a class="link" href="sql-statements.html#explain" title="13.8.2 EXPLAIN Statement"><code class="literal">EXPLAIN</code></a> is discussed in more
            detail in <a class="xref" href="sql-statements.html#explain" title="13.8.2 EXPLAIN Statement">Section 13.8.2, “EXPLAIN Statement”</a>.
          </p></li><li class="listitem"><p>
            Use <code class="literal">ANALYZE TABLE
            <em class="replaceable"><code>tbl_name</code></em></code> to update the
            key distributions for the scanned table. See
            <a class="xref" href="sql-statements.html#analyze-table" title="13.7.2.1 ANALYZE TABLE Statement">Section 13.7.2.1, “ANALYZE TABLE Statement”</a>.
          </p></li><li class="listitem"><p>
            <a class="indexterm" name="idm46734182969952"></a>

            Use <code class="literal">FORCE INDEX</code> for the scanned table to
            tell MySQL that table scans are very expensive compared to
            using the given index:
          </p><pre data-lang="sql" class="programlisting">SELECT * FROM t1, t2 FORCE INDEX (index_for_column)
WHERE t1.col_name=t2.col_name;</pre><p>
            <code class="literal">USE INDEX</code> and <code class="literal">IGNORE
            INDEX</code> may also be useful. See
            <a class="xref" href="optimization.html#index-hints" title="8.9.4 Index Hints">Section 8.9.4, “Index Hints”</a>.
          </p></li><li class="listitem"><p>
            Global and table-level <code class="literal">STRAIGHT_JOIN</code>. See
            <a class="xref" href="sql-statements.html#select" title="13.2.9 SELECT Statement">Section 13.2.9, “SELECT Statement”</a>.
          </p></li><li class="listitem"><p>
            You can tune global or thread-specific system variables. For
            example, start <a class="link" href="programs.html#mysqld" title="4.3.1 mysqld — The MySQL Server"><span class="command"><strong>mysqld</strong></span></a> with the
            <a class="link" href="server-administration.html#sysvar_max_seeks_for_key"><code class="option">--max-seeks-for-key=1000</code></a>
            option or use <code class="literal">SET max_seeks_for_key=1000</code>
            to tell the optimizer to assume that no key scan causes more
            than 1,000 key seeks. See
            <a class="xref" href="server-administration.html#server-system-variables" title="5.1.7 Server System Variables">Section 5.1.7, “Server System Variables”</a>.
</p></li></ul>
</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="table-definition-issues"></a>B.4.6 Table Definition-Related Issues</h3>

</div>

</div>

</div>
<div class="toc">
<dl class="toc"><dt><span class="section"><a href="error-handling.html#alter-table-problems">B.4.6.1 Problems with ALTER TABLE</a></span></dt><dt><span class="section"><a href="error-handling.html#temporary-table-problems">B.4.6.2 TEMPORARY Table Problems</a></span></dt></dl>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="alter-table-problems"></a>B.4.6.1 Problems with ALTER TABLE</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734182954912"></a><a class="indexterm" name="idm46734182953872"></a><a class="indexterm" name="idm46734182952384"></a><a class="indexterm" name="idm46734182950896"></a><p>
          If you get a duplicate-key error when using
          <a class="link" href="sql-statements.html#alter-table" title="13.1.8 ALTER TABLE Statement"><code class="literal">ALTER TABLE</code></a> to change the
          character set or collation of a character column, the cause is
          either that the new column collation maps two keys to the same
          value or that the table is corrupted. In the latter case, you
          should run <a class="link" href="sql-statements.html#repair-table" title="13.7.2.5 REPAIR TABLE Statement"><code class="literal">REPAIR TABLE</code></a> on the
          table. <a class="link" href="sql-statements.html#repair-table" title="13.7.2.5 REPAIR TABLE Statement"><code class="literal">REPAIR TABLE</code></a> works for
          <code class="literal">MyISAM</code>, <code class="literal">ARCHIVE</code>, and
          <code class="literal">CSV</code> tables.
        </p><p>
          If <a class="link" href="sql-statements.html#alter-table" title="13.1.8 ALTER TABLE Statement"><code class="literal">ALTER TABLE</code></a> dies with the
          following error, the problem may be that MySQL crashed during
          an earlier <a class="link" href="sql-statements.html#alter-table" title="13.1.8 ALTER TABLE Statement"><code class="literal">ALTER TABLE</code></a>
          operation and there is an old table named
          <code class="filename">A-<em class="replaceable"><code>xxx</code></em></code> or
          <code class="filename">B-<em class="replaceable"><code>xxx</code></em></code> lying
          around:
        </p><pre data-lang="none" class="programlisting">Error on rename of './database/name.frm'
to './database/B-<em class="replaceable"><code>xxx</code></em>.frm' (Errcode: 17)
</pre><p>
          In this case, go to the MySQL data directory and delete all
          files that have names starting with <code class="literal">A-</code> or
          <code class="literal">B-</code>. (You may want to move them elsewhere
          instead of deleting them.)
        </p><p>
          <a class="link" href="sql-statements.html#alter-table" title="13.1.8 ALTER TABLE Statement"><code class="literal">ALTER TABLE</code></a> works in the
          following way:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              Create a new table named
              <code class="filename">A-<em class="replaceable"><code>xxx</code></em></code> with
              the requested structural changes.
            </p></li><li class="listitem"><p>
              Copy all rows from the original table to
              <code class="filename">A-<em class="replaceable"><code>xxx</code></em></code>.
            </p></li><li class="listitem"><p>
              Rename the original table to
              <code class="filename">B-<em class="replaceable"><code>xxx</code></em></code>.
            </p></li><li class="listitem"><p>
              Rename
              <code class="filename">A-<em class="replaceable"><code>xxx</code></em></code> to
              your original table name.
            </p></li><li class="listitem"><p>
              Delete
              <code class="filename">B-<em class="replaceable"><code>xxx</code></em></code>.
</p></li></ul>
</div>
<p>
          If something goes wrong with the renaming operation, MySQL
          tries to undo the changes. If something goes seriously wrong
          (although this shouldn't happen), MySQL may leave the old
          table as
          <code class="filename">B-<em class="replaceable"><code>xxx</code></em></code>. A
          simple rename of the table files at the system level should
          get your data back.
        </p><p>
          If you use <a class="link" href="sql-statements.html#alter-table" title="13.1.8 ALTER TABLE Statement"><code class="literal">ALTER TABLE</code></a> on a
          transactional table or if you are using Windows,
          <a class="link" href="sql-statements.html#alter-table" title="13.1.8 ALTER TABLE Statement"><code class="literal">ALTER TABLE</code></a> unlocks the table
          if you had done a
          <a class="link" href="sql-statements.html#lock-tables" title="13.3.5 LOCK TABLES and UNLOCK TABLES Statements"><code class="literal">LOCK
          TABLE</code></a> on it. This is done because
          <code class="literal">InnoDB</code> and these operating systems cannot
          drop a table that is in use.
</p>
</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h4 class="title"><a name="temporary-table-problems"></a>B.4.6.2 TEMPORARY Table Problems</h4>

</div>

</div>

</div>
<a class="indexterm" name="idm46734182915504"></a><p>
          Temporary tables created with
          <a class="link" href="sql-statements.html#create-table" title="13.1.18 CREATE TABLE Statement"><code class="literal">CREATE TEMPORARY
          TABLE</code></a> have the following limitations:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
              <code class="literal">TEMPORARY</code> tables are supported only by
              the <code class="literal">InnoDB</code>, <code class="literal">MEMORY</code>,
              <code class="literal">MyISAM</code>, and <code class="literal">MERGE</code>
              storage engines.
            </p></li><li class="listitem"><p>
              Temporary tables are not supported for NDB Cluster.
            </p></li><li class="listitem"><p>
              The <a class="link" href="sql-statements.html#show-tables" title="13.7.5.37 SHOW TABLES Statement"><code class="literal">SHOW TABLES</code></a> statement
              does not list <code class="literal">TEMPORARY</code> tables.
            </p></li><li class="listitem"><p>
              To rename <code class="literal">TEMPORARY</code> tables,
              <code class="literal">RENAME TABLE</code> does not work. Use
              <a class="link" href="sql-statements.html#alter-table" title="13.1.8 ALTER TABLE Statement"><code class="literal">ALTER TABLE</code></a> instead:
            </p><pre data-lang="sql" class="programlisting">ALTER TABLE old_name RENAME new_name;</pre></li><li class="listitem"><p>
              You cannot refer to a <code class="literal">TEMPORARY</code> table
              more than once in the same query. For example, the
              following does not work:
            </p><pre data-lang="sql" class="programlisting">SELECT * FROM temp_table JOIN temp_table AS t2;</pre><a class="indexterm" name="idm46734182897072"></a><a class="indexterm" name="idm46734182895584"></a><p>
              The statement produces this error:
            </p><pre data-lang="none" class="programlisting">ERROR 1137: Can't reopen table: 'temp_table'</pre></li><li class="listitem"><p>
              The <span class="errortext">Can't reopen table</span> error also
              occurs if you refer to a temporary table multiple times in
              a stored function under different aliases, even if the
              references occur in different statements within the
              function. It may occur for temporary tables created
              outside stored functions and referred to across multiple
              calling and callee functions.
            </p></li><li class="listitem"><p>
              If a <code class="literal">TEMPORARY</code> is created with the same
              name as an existing non-<code class="literal">TEMPORARY</code>
              table, the non-<code class="literal">TEMPORARY</code> table is
              hidden until the <code class="literal">TEMPORARY</code> table is
              dropped, even if the tables use different storage engines.
            </p></li><li class="listitem"><p>
              There are known issues in using temporary tables with
              replication. See
              <a class="xref" href="replication.html#replication-features-temptables" title="16.4.1.29 Replication and Temporary Tables">Section 16.4.1.29, “Replication and Temporary Tables”</a>, for
              more information.
</p></li></ul>
</div>

</div>

</div>
<div class="section">
<div class="titlepage">
<div>
<div>
<h3 class="title"><a name="known-issues"></a>B.4.7 Known Issues in MySQL</h3>

</div>

</div>

</div>
<a class="indexterm" name="idm46734182883488"></a><a class="indexterm" name="idm46734182882000"></a><a class="indexterm" name="idm46734182880512"></a><a class="indexterm" name="idm46734182879024"></a><p>
        This section lists known issues in recent versions of MySQL.
      </p><p>
        For information about platform-specific issues, see the
        installation and porting instructions in
        <a class="xref" href="installing.html#general-installation-issues" title="2.1 General Installation Guidance">Section 2.1, “General Installation Guidance”</a>, and
        <a class="xref" href="extending-mysql.html#porting" title="28.5 Debugging and Porting MySQL">Section 28.5, “Debugging and Porting MySQL”</a>.
      </p><p>
        The following problems are known:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
            Subquery optimization for <code class="literal">IN</code> is not as
            effective as for <code class="literal">=</code>.
          </p></li><li class="listitem"><p>
            Even if you use <code class="literal">lower_case_table_names=2</code>
            (which enables MySQL to remember the case used for databases
            and table names), MySQL does not remember the case used for
            database names for the function
            <a class="link" href="functions.html#function_database"><code class="literal">DATABASE()</code></a> or within the
            various logs (on case-insensitive systems).
          </p></li><li class="listitem"><p>
            Dropping a <code class="literal">FOREIGN KEY</code> constraint does
            not work in replication because the constraint may have
            another name on the slave.
          </p></li><li class="listitem"><p>
            <a class="link" href="sql-statements.html#replace" title="13.2.8 REPLACE Statement"><code class="literal">REPLACE</code></a> (and
            <a class="link" href="sql-statements.html#load-data" title="13.2.6 LOAD DATA Statement"><code class="literal">LOAD DATA</code></a> with the
            <a class="link" href="sql-statements.html#replace" title="13.2.8 REPLACE Statement"><code class="literal">REPLACE</code></a> option) does not
            trigger <code class="literal">ON DELETE CASCADE</code>.
          </p></li><li class="listitem"><p>
            <code class="literal">DISTINCT</code> with <code class="literal">ORDER BY</code>
            does not work inside
            <a class="link" href="functions.html#function_group-concat"><code class="literal">GROUP_CONCAT()</code></a> if you do not
            use all and only those columns that are in the
            <code class="literal">DISTINCT</code> list.
          </p></li><li class="listitem"><p>
            When inserting a big integer value (between
            2<sup>63</sup> and
            2<sup>64</sup>−1) into a decimal or
            string column, it is inserted as a negative value because
            the number is evaluated in signed integer context.
          </p></li><li class="listitem"><p>
            With statement-based binary logging, the master writes the
            executed queries to the binary log. This is a very fast,
            compact, and efficient logging method that works perfectly
            in most cases. However, it is possible for the data on the
            master and slave to become different if a query is designed
            in such a way that the data modification is nondeterministic
            (generally not a recommended practice, even outside of
            replication).
          </p><p>
            For example:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p>
                <a class="link" href="sql-statements.html#create-table-select" title="13.1.18.4 CREATE TABLE ... SELECT Statement"><code class="literal">CREATE
                TABLE ... SELECT</code></a> or
                <a class="link" href="sql-statements.html#insert-select" title="13.2.5.1 INSERT ... SELECT Statement"><code class="literal">INSERT
                ... SELECT</code></a> statements that insert zero or
                <code class="literal">NULL</code> values into an
                <code class="literal">AUTO_INCREMENT</code> column.
              </p></li><li class="listitem"><p>
                <a class="link" href="sql-statements.html#delete" title="13.2.2 DELETE Statement"><code class="literal">DELETE</code></a> if you are
                deleting rows from a table that has foreign keys with
                <code class="literal">ON DELETE CASCADE</code> properties.
              </p></li><li class="listitem"><p>
                <a class="link" href="sql-statements.html#replace" title="13.2.8 REPLACE Statement"><code class="literal">REPLACE ...
                SELECT</code></a>, <code class="literal">INSERT IGNORE ...
                SELECT</code> if you have duplicate key values in the
                inserted data.
</p></li></ul>
</div>
<p>
            <span class="bold"><strong>If and only if the preceding queries
            have no <code class="literal">ORDER BY</code> clause guaranteeing a
            deterministic order</strong></span>.
          </p><p>
            For example, for
            <a class="link" href="sql-statements.html#insert-select" title="13.2.5.1 INSERT ... SELECT Statement"><code class="literal">INSERT ...
            SELECT</code></a> with no <code class="literal">ORDER BY</code>, the
            <a class="link" href="sql-statements.html#select" title="13.2.9 SELECT Statement"><code class="literal">SELECT</code></a> may return rows in a
            different order (which results in a row having different
            ranks, hence getting a different number in the
            <code class="literal">AUTO_INCREMENT</code> column), depending on the
            choices made by the optimizers on the master and slave.
          </p><p>
            A query is optimized differently on the master and slave
            only if:
</p>
<div class="itemizedlist">
<ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p>
                The table is stored using a different storage engine on
                the master than on the slave. (It is possible to use
                different storage engines on the master and slave. For
                example, you can use <code class="literal">InnoDB</code> on the
                master, but <code class="literal">MyISAM</code> on the slave if
                the slave has less available disk space.)
              </p></li><li class="listitem"><p>
                MySQL buffer sizes
                (<a class="link" href="server-administration.html#sysvar_key_buffer_size"><code class="literal">key_buffer_size</code></a>, and
                so on) are different on the master and slave.
              </p></li><li class="listitem"><p>
                The master and slave run different MySQL versions, and
                the optimizer code differs between these versions.
</p></li></ul>
</div>
<p>
            This problem may also affect database restoration using
            <span class="command"><strong>mysqlbinlog|mysql</strong></span>.
          </p><p>
            The easiest way to avoid this problem is to add an
            <code class="literal">ORDER BY</code> clause to the aforementioned
            nondeterministic queries to ensure that the rows are always
            stored or modified in the same order. Using row-based or
            mixed logging format also avoids the problem.
          </p></li><li class="listitem"><p>
            Log file names are based on the server host name if you do
            not specify a file name with the startup option. To retain
            the same log file names if you change your host name to
            something else, you must explicitly use options such as
            <a class="link" href="replication.html#option_mysqld_log-bin"><code class="option">--log-bin=<em class="replaceable"><code>old_host_name</code></em>-bin</code></a>.
            See <a class="xref" href="server-administration.html#server-options" title="5.1.6 Server Command Options">Section 5.1.6, “Server Command Options”</a>. Alternatively, rename
            the old files to reflect your host name change. If these are
            binary logs, you must edit the binary log index file and fix
            the binary log file names there as well. (The same is true
            for the relay logs on a slave server.)
          </p></li><li class="listitem"><p>
            <a class="link" href="programs.html#mysqlbinlog" title="4.6.7 mysqlbinlog — Utility for Processing Binary Log Files"><span class="command"><strong>mysqlbinlog</strong></span></a> does not delete temporary
            files left after a <a class="link" href="sql-statements.html#load-data" title="13.2.6 LOAD DATA Statement"><code class="literal">LOAD DATA</code></a>
            statement. See <a class="xref" href="programs.html#mysqlbinlog" title="4.6.7 mysqlbinlog — Utility for Processing Binary Log Files">Section 4.6.7, “<span class="command"><strong>mysqlbinlog</strong></span> — Utility for Processing Binary Log Files”</a>.
          </p></li><li class="listitem"><p>
            <code class="literal">RENAME</code> does not work with
            <code class="literal">TEMPORARY</code> tables or tables used in a
            <code class="literal">MERGE</code> table.
          </p></li><li class="listitem"><p>
            When using <code class="literal">SET CHARACTER SET</code>, you cannot
            use translated characters in database, table, and column
            names.
          </p></li><li class="listitem"><p>
            You cannot use <code class="literal">_</code> or <code class="literal">%</code>
            with <code class="literal">ESCAPE</code> in
            <a class="link" href="functions.html#operator_like"><code class="literal">LIKE ...
            ESCAPE</code></a>.
          </p></li><li class="listitem"><p>
            The server uses only the first
            <a class="link" href="server-administration.html#sysvar_max_sort_length"><code class="literal">max_sort_length</code></a> bytes when
            comparing data values. This means that values cannot
            reliably be used in <code class="literal">GROUP BY</code>,
            <code class="literal">ORDER BY</code>, or <code class="literal">DISTINCT</code>
            if they differ only after the first
            <a class="link" href="server-administration.html#sysvar_max_sort_length"><code class="literal">max_sort_length</code></a> bytes. To
            work around this, increase the variable value. The default
            value of <a class="link" href="server-administration.html#sysvar_max_sort_length"><code class="literal">max_sort_length</code></a> is
            1024 and can be changed at server startup time or at
            runtime.
          </p></li><li class="listitem"><p>
            Numeric calculations are done with
            <a class="link" href="data-types.html#integer-types" title="11.1.2 Integer Types (Exact Value) - INTEGER, INT, SMALLINT, TINYINT, MEDIUMINT, BIGINT"><code class="literal">BIGINT</code></a> or
            <a class="link" href="data-types.html#floating-point-types" title="11.1.4 Floating-Point Types (Approximate Value) - FLOAT, DOUBLE"><code class="literal">DOUBLE</code></a> (both are normally 64
            bits long). Which precision you get depends on the function.
            The general rule is that bit functions are performed with
            <a class="link" href="data-types.html#integer-types" title="11.1.2 Integer Types (Exact Value) - INTEGER, INT, SMALLINT, TINYINT, MEDIUMINT, BIGINT"><code class="literal">BIGINT</code></a> precision,
            <a class="link" href="functions.html#function_if"><code class="literal">IF()</code></a> and
            <a class="link" href="functions.html#function_elt"><code class="literal">ELT()</code></a> with
            <a class="link" href="data-types.html#integer-types" title="11.1.2 Integer Types (Exact Value) - INTEGER, INT, SMALLINT, TINYINT, MEDIUMINT, BIGINT"><code class="literal">BIGINT</code></a> or
            <a class="link" href="data-types.html#floating-point-types" title="11.1.4 Floating-Point Types (Approximate Value) - FLOAT, DOUBLE"><code class="literal">DOUBLE</code></a> precision, and the
            rest with <a class="link" href="data-types.html#floating-point-types" title="11.1.4 Floating-Point Types (Approximate Value) - FLOAT, DOUBLE"><code class="literal">DOUBLE</code></a> precision.
            You should try to avoid using unsigned long long values if
            they resolve to be larger than 63 bits (9223372036854775807)
            for anything other than bit fields.
          </p></li><li class="listitem"><p>
            You can have up to 255 <a class="link" href="data-types.html#enum" title="11.3.5 The ENUM Type"><code class="literal">ENUM</code></a>
            and <a class="link" href="data-types.html#set" title="11.3.6 The SET Type"><code class="literal">SET</code></a> columns in one table.
          </p></li><li class="listitem"><p>
            In <a class="link" href="functions.html#function_min"><code class="literal">MIN()</code></a>,
            <a class="link" href="functions.html#function_max"><code class="literal">MAX()</code></a>, and other aggregate
            functions, MySQL currently compares
            <a class="link" href="data-types.html#enum" title="11.3.5 The ENUM Type"><code class="literal">ENUM</code></a> and
            <a class="link" href="data-types.html#set" title="11.3.6 The SET Type"><code class="literal">SET</code></a> columns by their string
            value rather than by the string's relative position in the
            set.
          </p></li><li class="listitem"><p>
            In an <a class="link" href="sql-statements.html#update" title="13.2.11 UPDATE Statement"><code class="literal">UPDATE</code></a> statement,
            columns are updated from left to right. If you refer to an
            updated column, you get the updated value instead of the
            original value. For example, the following statement
            increments <code class="literal">KEY</code> by <code class="literal">2</code>,
            <span class="bold"><strong>not</strong></span> <code class="literal">1</code>:
          </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>UPDATE <em class="replaceable"><code>tbl_name</code></em> SET KEY=KEY+1,KEY=KEY+1;</code></strong>
</pre></li><li class="listitem"><p>
            You can refer to multiple temporary tables in the same
            query, but you cannot refer to any given temporary table
            more than once. For example, the following does not work:
          </p><pre data-lang="sql" class="programlisting">mysql&gt; <strong class="userinput"><code>SELECT * FROM temp_table, temp_table AS t2;</code></strong>
ERROR 1137: Can't reopen table: 'temp_table'
</pre></li><li class="listitem"><p>
            The optimizer may handle <code class="literal">DISTINCT</code>
            differently when you are using <span class="quote">“<span class="quote">hidden</span>”</span> columns
            in a join than when you are not. In a join, hidden columns
            are counted as part of the result (even if they are not
            shown), whereas in normal queries, hidden columns do not
            participate in the <code class="literal">DISTINCT</code> comparison.
          </p><p>
            An example of this is:
          </p><pre data-lang="sql" class="programlisting">SELECT DISTINCT mp3id FROM band_downloads
       WHERE userid = 9 ORDER BY id DESC;</pre><p>
            and
          </p><pre data-lang="sql" class="programlisting">SELECT DISTINCT band_downloads.mp3id
       FROM band_downloads,band_mp3
       WHERE band_downloads.userid = 9
       AND band_mp3.id = band_downloads.mp3id
       ORDER BY band_downloads.id DESC;</pre><p>
            In the second case, you may get two identical rows in the
            result set (because the values in the hidden
            <code class="literal">id</code> column may differ).
          </p><p>
            Note that this happens only for queries that do not have the
            <code class="literal">ORDER BY</code> columns in the result.
          </p></li><li class="listitem"><p>
            If you execute a <code class="literal">PROCEDURE</code> on a query
            that returns an empty set, in some cases the
            <code class="literal">PROCEDURE</code> does not transform the columns.
          </p></li><li class="listitem"><p>
            Creation of a table of type <code class="literal">MERGE</code> does
            not check whether the underlying tables are compatible
            types.
          </p></li><li class="listitem"><p>
            If you use <a class="link" href="sql-statements.html#alter-table" title="13.1.8 ALTER TABLE Statement"><code class="literal">ALTER TABLE</code></a> to add
            a <code class="literal">UNIQUE</code> index to a table used in a
            <code class="literal">MERGE</code> table and then add a normal index
            on the <code class="literal">MERGE</code> table, the key order is
            different for the tables if there was an old,
            non-<code class="literal">UNIQUE</code> key in the table. This is
            because <a class="link" href="sql-statements.html#alter-table" title="13.1.8 ALTER TABLE Statement"><code class="literal">ALTER TABLE</code></a> puts
            <code class="literal">UNIQUE</code> indexes before normal indexes to
            be able to detect duplicate keys as early as possible.
</p></li></ul>
</div>

</div>

</div>

</div>
<div class="copyright-footer">

</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left"><a accesskey="p" href="faqs.html">Prev</a></td>
<td width="20%" align="center"><a accesskey="u" href="">Up</a></td>
<td width="40%" align="right"> <a accesskey="n" href="indexes.html">Next</a></td>
</tr>
<tr>
<td width="40%" align="left" valign="top">Appendix A MySQL 5.7 Frequently Asked Questions</td>
<td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td>
<td width="40%" align="right" valign="top">Appendix C Indexes</td>
</tr>
</table>
</div>
</body>
</html>
